>I'm interested in any solutions to problem of distributing update .exe and
>..dbc files to client. Right now we have a user in the client network with
>access to all machines in the network copy the latest versions to the
>client computers across NT networks. This is becoming tedious, of course.
>
>I'm thinking of something like a program that the user launches instead of
>the application .exe that checks the version and determines if the user
>needs a new version, downloads it to the client machine and then launches
>it -- or some variation on this process.
>
>Has anyone done this successfully? And would you share your process? TIA
>- Gail

My app install also installs a small .exe that checks the dates of the main app and the app in the update directory on the server. If the server version is newer, the program copies it over to the workstation. This program is put in every workstation's startup folder so it runs when the user turns on the computer. In addition, the first line of the main program checks the same file dates and informs the user if their copy is out of date.

As for updated .dbcs, I'm not sure exactly what your situation is, but if your dilemma involves getting updated table structures from your computer to the client's, you should check out Stonefield's Database Toolkit. It has a utility that the client can run that updates all of the tables and dbc from update files that you send them.