Rick, suggested the same thing. But our version 3.15, this functionality is not available or doesn't work properly. We've suggested upgrades to our client but as of right now we have not been able to convince them to upgrade to the latest version of WConnect.

>Why go to all that trouble? Set the directory where the updated EXE is and the production folder of where to copy the new EXE to. Then use the Admin utility to have WC shut down the servers and copy the new EXE over the old one. That way there is no need to switch to File mode then back to COM based.
>
>>We have an older versioin of Web Connect running on an NT 4.0 box. When updating the EXE, I have been taking the following steps:
>>1. Set Message mode to File Based.
>>2. Rebuild the EXE.
>>3. Set Message mode to Automation.
>>4. Load Servers.
>>Recently, I've been having problems with the build of the EXE hanging. I've had to close down FoxPro and when I try to re-open the project, the project file has become corrupted. I've then recopied up the project file and rebuilt successfully.
>>
>>We have had to reboot the machine 2 days in a row after doing updates.
>>
>>I don't know if the 2 are related but we were getting the following error before the system had to be rebooted:
>>
>>The server {1FCBD263-25B7-11D4-B64C-0050DAD523CC} did not register with DCOM within the required timeout. Event Id: 10010
>>
>>We then get a Event ID: 2000 which is associated with denial of service.
>>
>>Any help with these problems would be greatly appreciated.
>>
>>
>>TIA