Hi Yau,

I have run into similar problems and what I have done is to load all tables and views for all lookups when the form is instantiated but I load the form at app startup and hide it. When the user clicks on a button or a menu option to run the form it is actually brought up and maximized on top of all other forms and is instantaneous. When the user closes the form, it is hidden again and not actually closed. A timer does requeries to refresh the data. The form is not in edit mode by default, the user has to click on an edit button to edit a record so no data has ever been corrupted this way over a WAN even. Since it is all buffered data anyway (and each workstation has a battery backup for power outages) and all changes are saved or cancelled by force before closing (actually hiding) the form. To do it this way you must step through all open forms and close each one before the app is exited (a good practice anyway) and before opening the form, checking for its existance and if it is already an object, bring it forward instead of opening it.


>Thanks Hilmar, will definitely try out your suggestions.
>However, this approach has its risks in that if there's a power failure (with no UPS), it could result in serious data corruption.
>Yau