acDialogue type performance

  • Thread starter Thread starter smk23
  • Start date Start date
S

smk23

For performance reasons, I have forms go invisible rather than close when a
user makes a selection and then clicks close. Is there any way to get
dialogue form functionality. I.E. I'd like to return to the calling code and
continue from there.

Thanks,
Sam
 
smk23 said:
For performance reasons, I have forms go invisible rather than close when a
user makes a selection and then clicks close. Is there any way to get
dialogue form functionality. I.E. I'd like to return to the calling code and
continue from there.

Thanks,
Sam
Click to expand...

Probably not.

You can start to do this really easily: open the form as dialog, make the
form
invisible, the calling code continues. But you can't switch the form back
to
dialog: you have to close it to switch it back to dialog, which is not what
you
want.

You have to code it.

I do it by passing a function name to the hidden form when I unhide it.
After
the form hides itself, it calls the function name to continue. It is very
tricky,
Much harder than it sounds, getting all the events to work correctly. It
probably would be not so bad if all the forms were simple, but if I had a
simple system, I wouldn't be working with hidden dialog forms... This is
the form equivalent of having circular references, it is really difficult to
work
with, not a good way to go.

(david)
 
smk23 said:
For performance reasons, I have forms go invisible rather than close when a
user makes a selection and then clicks close. Is there any way to get
dialogue form functionality. I.E. I'd like to return to the calling code and
continue from there.
Click to expand...


Another ugly approach is for the calling code to poll the
pseudo dialog form's visibility:

With Forms![funky dialog form]
.Visible = True
Do Until .Visible = False
DoEvents
Loop
End With
 
Back
Top