I have had success using delayed instantiation. Also, I have in the past displayed a message while the form loads (or load it in the background when the user starts the app and hide it while other events are happening) and when the user closes the form, hide it instead of actually closing it. The delay is only occuring once then. Then when the user elects to open the form again, you only need to show the hidden form and it is instantaneous. Of course, when the user closes the app, you have to step through all open forms and close them since the form is open but hidden. If the app slows down while the form is open though, you should step through the form's events and see if any events are running multiple times or where the actual 'slag' is. Additionally, do your listboxes and comboboxes use parameterized views or tables? Opening large tables or views for comboboxes can really slow a form down and use up resources.

Tracy

>I have a screen that has many objects on several tabs. It includes many combo-boxes, lists, grids using various cursors, tables, and tempoarary files.
>
>There seems to be a very definate limit on how may objects a screen can have that are bond to cursors and/or files. There are two things that seems to happen consistantly. 1) The screen is displayed as an empty window as if there is not enough resouces to complete the activation, 2) performance crawls.
>
>Any comments? The only way I can reduce the number of open cursors/files on this screen is to move some of them to other pop-up screens which I'd rather not do for user friendly and navigation speed reasons.