I had a similar problem in that if the date/time stamp of the
client APP was greater than the Server's date/time stamp
I would issue an error message (since the Client software
should never be more current than the server). I found that
with a NT server and WinNt/Win98 clients that the time could
be upto 5 seconds different. After I allowed for this potential
time difference I have not had a problem.
====================================================================
>>>Bruce,
>>>
>>>Try RUN /N c:\etc\myapp.exe. Your little startup EXE can now terminate. It will probably reload the VFP run-time, so you may see a performance hit, but disk caching will probably reduce that quite a bit since you just loaded the run-time when your startup app loaded.
>>
>>Thanks, that works fine, there doesn't appear to be much performance hit...
>
>
>Hi Bruce,
>
>I have the same "exact" problem you had with the need to frequently modify the main .exe on the server and the launcher.exe(at times). the main.exe is run from the local machines and if I throw out another new main.exe on the server that is newer than the users local machine has, the launcher.exe will copy the latest version to their local machine. My launcher.exe doesn't always detect that the network.exe is more recent than the local.exe though. Would you be willing to shoot me the piece of code that checks for most recent exe? I am interested in what approach you took to compare datetime for exe. BTW - That run command works fine for me also...thanks Josh!
>
>Thanks.
>
>John