Problem: I have two forms running modal. You can jump from form 1 to 2 and 2 to 1. When users close 2, it jumps back to 1 automatically. Form 2 will stop to respond if you jump back and forth by closing form 2 couple of times.
I guess because of the modality of showing form 1, the termination code was never completely executed. It is fine to suspend the execution of codes with other events, but somehow Microsoft thought you cannot terminate twice.
In MS Access you can open a modal form and continue to execute the codes. I like that approach better. Why suspend execution of codes because of modality? That takes away some power from the programmers and adds extra burden to memory usage. If the users jump from one modal form to another many times, there are a lot of continuing codes to be executed and most of the time such codes are "end sub" type statements.
I think there should be a command that load modal forms and continue to execute the subsequent codes, or build the show method with such an option.
I guess because of the modality of showing form 1, the termination code was never completely executed. It is fine to suspend the execution of codes with other events, but somehow Microsoft thought you cannot terminate twice.
In MS Access you can open a modal form and continue to execute the codes. I like that approach better. Why suspend execution of codes because of modality? That takes away some power from the programmers and adds extra burden to memory usage. If the users jump from one modal form to another many times, there are a lot of continuing codes to be executed and most of the time such codes are "end sub" type statements.
I think there should be a command that load modal forms and continue to execute the subsequent codes, or build the show method with such an option.