>What version of SDT are you using?

- Im using SDT 5.1j

>
>The Update folder is just a temporary location for the SDT files. This is the way I do it and it works flawlessly. You do NOT run the SDT Update on the files in the Update folder. The reason I do it this way is so the customer can determine when it is OK to update the database since this requires exclusive use of tables.
>
>When the user starts my databse update process, my app tries to exclusively open a table that is always opend by the app when launched. If this is successful, then I know ALL users except this one is completely out of the app.
>
>My app then copies the SDT tables and DBC files from the Update folder to the folder where the real data resides. If the copy is successful, my app deletes all the SDT and DBC files in the Update folder. I then issue the oMeta.oSDTMgr.OpenData() method to open and set the database.
>
>All that is left is to issue the oMeta.oSDTMgr.Update() method.
>
- I thought I could use the code as it was written in Visual Extend. The update process is automatically called when the app opens if needed, so my customer has no way to prevent this. I didn't realize that I needed to change how it handled updates, but I can see that there must be a problem with the framework. Your solution makes sense. Thanks for your help!

PS. Great your crying towel out for tonights game. <bg>

Sandi.