>>I know I've seen this addressed before, but what would be the cleanest way to do the following without disrupting the running of the application:
>>
>>1. Update the EXE if it exists on the PC
>>2. Update the EXE if it exists on the server
>>3. Update the DBC if table structures have changed
>>
>>I have looked at the many loader programs available, but it's hard to decide which is best, or if it is actually better to write my own process. Thanks!
>>
>>Regards, Renoir
>
>I do the following, and it works fine:
>
>

I keep the EXE on the server, since this makes updating easier.
>

However, each user has run-time installed, since this doesn't update so frequently. Besides, I got sick of having so many duplicates on the server (separate maintenance programs in different folders).
>

A loader program detects and loads the latest version of the executable, marked by a number (as part of the filename). Details (including source code) on request.
>

When updating the EXE on the server, I save it with the next number available.
>
>

Data is updated at midnight. For this purpose, I have an empty copy of the database, do my changes there, and basically do APPEND FROM (from the official data to the new structure) for modified tables. Parent tables have to be copied before child tables, or else you'll get "trigger failed" on insert.
>
>HTH, Hilmar.

Hilmar (and anyone else reading),

One of my needs is that this particular system is a 24/7 operation and I need to find a way to update the application/data without knocking anyone off...if possible. If data structures change while someone is using an application it seems to me that this would cause all kinds of problems. There must be a way...

Also, a coworker just mentioned that he thought that since Foxpro reads "portions" of an EXE into memory instead of the whole thing that this could cause problems with scrambling the application in memory. I had never heard that I am dubious of it's validity, but wanted to see if others had anything to add about that.

Renoir