>>>>Hi,
>>>>
>>>>I develop apps specifically for our company rather than a bunch of different clients. Frequently, I make changes to the code that does not impact the data structures. I've been using a batch file to copy the latest .exe from the server to the local drive and then execute it, thus ensuring that everyone gets the latest .exe on startup.
>>>>
>>>>But this leaves an ugly black DOS box running (and an additional program on the task bar) that I'd like to eliminate.
>>>>
>>>>I'd like to know how you all accomplish this type of update.
>>>>
>>>>TIA
>>>
>>>
>>>Create a loader program that looks for the newest actual EXE on the server. If one is found, it is copied down to the local drive, then the loader just does DO Real.EXE.
>>
>>Then the loader exits, or does it keep running until Real.exe exits?
>>
>>Thanks
>
>
>It keeps running, but it's really small...only a dozen lines of code, so it doesn't matter.

Expanding on Craig's answer, how about moving all your code out of the real EXE into an APP. The real EXE on startup checks a well known location on the server for a DBF that contains a list of files that need to be copied to the WS if there is a change. In the DBF is a timestamp and file size for the current correct APP. If the APP on the WS is not there or is early, the EXE copies the APP in question to the WS. Then the EXE calls 'do ("mainapp.app")' (the parens and quotes prevent the EXE from storing a reference to the APP when it is compiled. You could even use this DBF in the well known location for the name of the main app to run (maybe that's too far).

Roger