Tore,

Thanks for the reply.

Here are some things on my mind:

1- So I take it that MYAPP.exe is different from MYLOADER.exe?
2- Can one do it in such a way that MYLOADER functionality is built-into MYAPP.exe? I tried doing this but since MYAPP.exe is open it obviously results in an error message (File is being used).

Sincerely,

Dennis

>Dennis,
>
>I guess Sergey is sleeping, so I take the liberty to answer your question. The "loader" program:
>1. Check if the local file(s) are older than the server files
>2. If yes to 1, copy the new files from the server to the local machine
>3. Often the program also does some other stuff, like making sure that local directories exist and so on
>4. Start the local EXE. For logical reasons, the local EXE always another name than the "loader" application.
>
>If done properly, the "loader" program never changes. Personally my loader program scans a VFP table which contains instructions of what to do, and which program to start.
>
>>Sergey,
>>
>>Thanks for the links! Can't wait to check them out. How are they done in principle?
>>
>>Sincerely,
>>Dennis
>>
>>
>>>Check
>>>

AppStart - Auto-Update Application Starter File #21770
>>>

Simple application launcher File #9668
>>>

Application Launcher File #9627
>>>
>>>>
>>>>It's getting to be tedious to copy the latest version EXE files of an app to all client PCs. Is there any way for an EXE to automatically detect if there is a newer version on a centralized location and then update itself by itself?
>>>>