I have seen this before and rather than reinvent the wheel, we loaded all forms when the app started up and hid them. When a user needed a form following app startup, the form was made visible instead of loaded from scratch. When the user closes a form, the form was actually hidden instead of closed. The trick is to load them all at the beginning, hide them, and then when the form is opened later, just make it visible instead of loading it. The closedown portion must be rewritten though to step through all open forms and close them. There is a delay during app startup which can be handled with messages to the user, splash screens, etc. The use of the app throughout the day though should exhibit no delay.


>I inheritted an application that is installed on a computer - desktop or server - doesn't matter. That folder is then shared with Windows and multiple clients connect to it - up to 15 but usually only 3-4. The executable is about 11 megabytes and the foxpro dll's are in that folder as well. When the tables start getting over 2-3 megs each, processes in the application start to run REALLY slowly. The worst is when a view is in a dataenvironment that opens a few tables joined together.
>
>What is the best way to deal with this besides re-writing the application to run from SQL server? Any ideas?
>
>Randy Wessels