>You do not provide the new, empty, tables to your customer.

All you do is copy the new SDT tables and the 3 database files [DBC, DCX and DCT] into your customer's data folder.
- That is all I put in the update directory. The program built new empty files in the update directory after the UPDATE routine ran. I have no idea why???


You also should open nothing in the Update folder. This is just a temporary location for the new SDT and database files. After they are copied to the production data folder, they should be deleted from the Update folder. Then just open the database and run the SDT Update method.
- I didnt do anything in that directory. I just noticed that:

First time I ran application the Update directory contained SDT meta files and DBC files. Application ran and did the SDT Update routine. It created empty versions of free files in the Update directory. It removed the DBC and SDT meta files from the UPdate directory. So After Application completed openning the Update directory only contained the empty free table files that IT created.

I exited application and looked at the free table VFXSYS in the data directory. It still contained my data but the data structure had not been updated. I looked at the empty file in the UPdate directory that it had created, and it contained no data and the correct structure.

I figured maybe it would fix it the next time I ran the app, so I ran the app again and it did not fix anything, it made it worse because once it was done the data directory contained the empty new structure, the update directory was empty.

**
When I freed the files from the DBC (in StoneField Explorer) and regenerated the metafiles, I looked at the meta file - COREMETA and it showed the tables in question as not being related to the dbc and containing the correct data structure.I looked at the SDTMETA file and it also shows the tables in question as not being releated to a dbc and containing the correct data structure.

While both the COREMETA and the SDTMETA files look the same with respect to the tables in question, I noticed that one other table is different. I have a table which is in the DBC, but the COREMETA does not contain the dbc name in the dbc field. The SDTMETA correctly contains the dbc name.

Have I somehow 'confused' the meta files/dbc to the point that the SDT Update routine cannot properly run?

Sandi