Userfrom Property ShowModal = False

The sample workbook is attached.

When the workbook opens, the userform will automatically show.

Issue at this point: if other workbooks are open before opening the attached workbook, it is not able to do anything on other workbooks.

Close the userform, then reopen the userform by clicking the command button, now it is okay to do something on other workbooks.

WHY....?

Attached: By the way, how to get rid of the things in red rectangle?

Even a brand new workbook comes with them, and I don't even know where they came from. I don't even have password for SOLVER.

Thanks.

------

Never mind, is it from Add-In? Just leave it alone.

If you look in ThisWorkbook module, the WorkBook_Open event ... you have the UserForm loading as Modal.

Delete the word "Modal"

Originally Posted by Logit

If you look in ThisWorkbook module, the WorkBook_Open event ... you have the UserForm loading as Modal.

Delete the word "Modal"

Thanks much!!!

You are welcome !

Originally Posted by Logit

You are welcome !

There is still an issue. Let us say I have a second userform (Property ShowModal = True), and there is command button on second userform (Unload Me; FormLogin.Show) to return to the initial userform. What does "Unload Me" do? Does it really CLOSE the userform? It seems second userform still prevents me from working on other workbooks.

I need to have second useform Property ShowModal = True

BUT if I simply close the second useform by clicking system red X in the top right corner, it does not have the issue. It seems Unload Me is different from X in the top right corner.

The following information may be reveiwed at : http://http://gregmaxey.com/word_tip...nced_tips.html

Look just a few paragraphs down the page and begin reading. Good information and better than I could explain.

Understanding Call Methods

Now that you understand the difference between the default instance and an explicit declaration instance of a form, I want to discuss methods of calling both types and the behavior observed in both with respect to the VBA Load and Set statements, and the userform .Show method, Initialize and Activate events.

Modal Forms

The easiest way to do this is with a series of demonstrations and experiments. To set up the demonstrations, perform these steps:

The article specifically speaks to unloading a UserForm and using the X (upper right corner) to close the form.
It also speaks to the command : " Set UserForm = Nothing "

Please Login or Register  to view this content.

Using the command " Set yourobject = Nothing " is not something I routinely use but perhaps I should ? In your case, it may assist with the issue of a closed Modal form still retaining
focus.

I created a sample project here with a UserForm and attempted to recreate what you are experiencing there. The UserForm displaying as Modal, then closing with a command button using
the command " Unload Me " vs using the X on the form. I also tried the command UserForm.Hide . Nothing here allowed the UserForm to remain in memory and retain the Modal property
preventing accessing other parts of the project.

Please Login or Register  to view this content.

Are you using some other command to close the UserForm ?

Just as little clarification (didn't read all the posts)

Loading a userform without specifying the mode loads it Modally... in other words:

Please Login or Register  to view this content.

Are the same thing.

To show it modelessly then that must be specified

Please Login or Register  to view this content.

Originally Posted by Logit

The following

Thanks. I will try Set = Nothing tomorrow. I have only Unload Me to close the second userform, but of course there is some other code(for other tasks) before closing the userform.

Originally Posted by Logit

The fol

Please Login or Register  to view this content.

What is frmBasic? Is it form name? In my case, it is FormLogin? Dim oFrm AS .... ? I thought AS should be followed by data type.

Thanks.

Very True, but it's True by default and (in my experience) very few actually even know it exists in the Properties dialog so it never gets changed. I can't remember an instance where even experienced coders use the Property rather than specifying the ShowMode on loading.

I guees I should have added 'In general...'

Originally Posted by VAer

Thanks. I will try Set = Nothing tomorrow. I have only Unload Me to close the second userform, but of course there is some other code(for other tasks) before closing the userform.

It may have something to do with first userform FormLogin, before showing second userform, I Unload FormLogin. Since it is Log In form, there is connection data, but I have set them to Nothing in FormLogin.

Originally Posted by xlnitwit

Yes, it is the form name. The form is itself a class (and interface) so you can create one or more instances of it, as with any class. Userforms are auto-instantiating, which is why you can refer to them as intrinsic objects without having to create a New instance, though it is regarded by many as better practice to do so.

Thanks. Good to know that it is okay to write "Dim .... AS FormName "

Originally Posted by VAer

What is frmBasic? Is it form name? In my case, it is FormLogin? Dim oFrm AS .... ? I thought AS should be followed by data type.

Thanks.

Just a " pic " from the website. Not my coding....

However, those form names are simply variables used to identify the form/s.