>>I have an existing exe running off of a server, with the tables in subdirectories below the exe directory (as discussed in an earlier thread - to permit security right assignments to the various tables).
>>
>>As I work on updating the exe to VFP6, I've seen discussions here in UT about placing a copy of the exe on each users PC to speed performance.
>>
>>How do I ensure that the exe can find the tables on the server?
>
>We use an INI file that is created during setup with an entry that points to the data directory. We read the file on app startup, then set paths accordingly. We also point private datasessions to it in the BeforeOpenTables event of each form's datasession. We keep the default directory pointed to the local machine, for temp files, etc.
>
>There are many ways do do it, this is only one.

This is similar to what we do. We use a config.dbf on each user's machine and have pointers to several different locations. We also point to the proper locations in the BeforeOpenTables event. I think this (INI or DBF configuration file) is the best way to go. If a server has a hard drive crash, you can restore the backup to a different network location, change the configuration, and you are up and running.

One thing I like about this is that we have the same EXE in different locations on each user's machine. One configuration points to the real data. One points to a set of test data (usually local and a day or two old). If a user is unsure of how to do something, or has a "what if" question, he/she can go into the test data and try things without damaging the real, live data. This could be done with INI files too.

One suggestion to Phil: If you have look-up type of tables that are static, you may want to place those on each local hard drive. This is be faster than accessing them through the network.

Joe