>I like Bob's approach - clean and pretty client proof. You just have to make sure that the client actually runs the update.
>
>Also, if you're onsite with a laptop, you can attach to the client's network and use you're version of QA or SEM.
>
>-Mike

We actually release a new .EXE with each db update. The .EXE compares the .EXE version with the database version from a field in the database that we update in the update (heh heh). If the version are out of sync our .EXE doesn't run. Which will force the user to run the dbupdate.

BOb