>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
I think you may wish to look at the Stonefield Database Toolkit. While you can create the necessary SQL and dbget/set props for the database container Doug Hennig has done a great job of providing methods such as determining which tables have changed an updating the target site etc. It's DBCX and CodeBook compatable and save me alot alot of work for a very nominal fee. We have been very successful at sending only the changed DBCs and have the client site resync itself as our app first starts up. If there are related data changes we handle them on the fly while amusing the user with some avi's.
HTH
Gary
We have really focused on only creating what is new and using well constructed components where every possible. Since most of these are royality free the expense versus development time and quality make assembly of components (including alot of our own) the only sane way to go.
My Opinion Only
Gary :-)