>I've tried to find a new way to use lookup tables. Now, I have a view for each lookup tables. It works fines but it's pretty slow each time I load a form. I used that method because it will be stored in a remote database.
>Another way is to store all the information in arrays (properties in oApp). But I'm afraid that it will eat a lot of memory. Some lookup tables have 1000 records and I have about 40 lookup tables.
>The last way I know is to make another LOCAL database and refresh it from the remote database (each day).
>
>I am looking for new ways. Any help will be a lot appreciated.

An application that I wrote a while back used 3 local lookup tables that were partial copies of tables on the server. I only copied those fields that were required for lookups and then pulled the remaining data off the server at run time, where needed. 2 were small tables, one had 40,000 records. Every workstation 'checked into' a system table on the server. The table kept track of last time downloads were successful and also a flag which would enable the SA to force a download for any given machine. A routine would fire each time the app was started and checked the 'check in' table to determine if a download was necessary. If so, the App would repopulate the local tables.

An alternative that we never really investigated would be to have the download routine called by the autoexec or some other system event controller.

HTH