Escape key on UserForm also cancels the next UserForm to appear?

I have a project where two UserForms are shown in succession. Form1 autocloses and then Form2 is loaded almost immediately afterwards.

But if the user presses escape while Form1 is shown, Form1 closes and Form2 never appears.

How do I work around this problem while still allowing Form1 to be closed with escape key?

Is there something I could code in between Form1.Show and Form2.Show to help negate the Escape key action on Form1 carrying onto Form2?


(Not sure is this helps: Form1 is shown Modal. Form2 is shown Modeless. I want to keep Form2 as modeless.)

Originally Posted by BigBas

Could you possibly include the Form2.Show code in the Form1_Deactivate event?

I didn't test this, but am wondering if it would work.

Hi BigBas, I appreciate your suggestion however I'd prefer not to use this approach. I try to keep my forms encapsulated. Form1 is a template I reuse between projects. Form2 is unique to the current project. (If there is no other solution, I will end up using this but I am hoping there is another way to fix it)

I'd suggest you provide some code showing how your forms are loaded and unloaded or a sample workbook, and maybe stipulate all your exclusions up-front.

Good to hear from you romperstomper. (BTW see my forum user description - I accepted 100% what you said a while ago!)

Originally Posted by romperstomper

I'd suggest you provide some code showing how your forms are loaded and unloaded

OK here's the code. Form1 = Splash. Form2 = Menu1

This is calling sub that loads these 2 forms

Please Login or Register  to view this content.

Here's the code for Form1 (it's a splash screen)

Please Login or Register  to view this content.

Here's the code for loading Form2 (aka Menu1)

Please Login or Register  to view this content.

And finally here's the code for Form2 (Menu1)

Please Login or Register  to view this content.

Originally Posted by romperstomper

maybe stipulate all your exclusions up-front.

Yes I agree. I overlooked specifying the encapsulation requisite upfront. My fault entirely. (Concepts that I use as a matter of course I sometimes overlook specifying as a requirement in threads ).

Exclusions:

• Forms to be encapsulated. Form2 should not be loaded from Form1
• Form1 must be able to be canceled with the Escape key
• I want to keep Form2 Modeless (I don't care about Form1 - it can be either)

Originally Posted by Kyle123

FWIW I find your reliance on errors simply to enable a user to press Escape to close a form a bit nasty.

Ah. I recently encountered the concept of having the Escape key trigger an Error Handler and I really like the idea (because it guarantees that the procedure will clean up properly if the end user presses cancel while a macro is running).
I think I got carried away with the newly encountered concept (as I always do) and I started applying this to forms as well. I'm now thinking that's not a good idea on forms (read on to see why!)

Originally Posted by Kyle123

As to why the code doesn't work when you've pressed the Esc key I don't know

I took your code - or rather the parts I wanted to keep - and it now runs perfectly. Pressing Escape now doesn't trigger a skip on the next form to appear! Thanks Kyle for coming to the rescue again! +1

It looks like your hunch re errors and Esc Key was right on the mark.

Originally Posted by Kyle123

I suspect your method of stopping a bus by driving it off a cliff isn't helping

ROTFL. I like your analogy!

Originally Posted by mc84excel

Good to hear from you romperstomper. (BTW see my forum user description - I accepted 100% what you said a while ago!)

Ha - I like it!