You could write the code to programically change the tables. I might suggest having a configuration file with some type of version indicator. When you send an update, you could have code at the initialization of the program to check the version in the configuration. If it is older than the "new" version, call the update table code (and update the version number in the config file).

Either that or just send a separate update tables program that should be run before the new .EXE is run.


>I just installed an .exe on a server. Workstations are accessing their own .exe from individual folders on the server. The tables and DBC are located in another folder. These are accessible are used from each workstation. I zipped the tables and DBC on separate disks and loaded them separately. The .exe and conf files were included in the setup disk (which also loaded all of the Fox drivers needed for installation on each workstation.) The shortcut on the workstation computer is addressed to each respective folder. VFox5 doesn't exit on the server or the individual workstations. So far that part is working.
>
>I would like to know if anyone knows how to get project changes and updates back to the server WITHOUT having to reload the tables and DBC. I want to be able to take a new .exe to the server with any table changes that I've made. The last time I did this the DBC didn't get updated and couldn't read my tables. Is there an easier way? I will have live data on-line shortly and can't afford to lose it. Any thoughts?
>
>I'm developing the project on a computer NOT connected to the network.
>
>Thanks
>Linda