Oh, man! If I had been paying attention to where you are from, I never would have replied! < bg > Hey, you got a bunch of goons playing up there. Weight and Smith should be suspended for their head hunting last night. Hell, Hatcher was suspended 2 games for less brutality.

Now for the serious stuff:

Put REMOVE TABLE MYTABLE in the UPDATE.PRG, compile it and send it with the DBC update files. See the VFP Help on the REMOVE TABLE command for more information.

>OK, I see how you handle needing to execute onetime code, this is similar to how SDT worked in 2.6. What code do I put into this program in order to free up a database, since the existing dbf file was part of the database DBC and within this new exe it has been turned into a free table.
>
>PS. I see you're a Dallas fan. I'll be watching your guys on Thursday from Edmonton, we're a pretty crazy group of Oiler fans up here!
>
>Sandi
>
>
>
>>What I would do is add some code to your startup MAIN.PRG to check for the existence of an UPDATE.FXP file. If it exists, the issue a DO UPDATE.FXP command followed by a ERASE UPDATE.FXP command. In the UPDATE.prg put code that needs to be run only once. The code you should run in this instance is REMOVE TABLE MyTable See VFP Help on this command for more info. The following is how I handle sending database updates to my customers.

>>local llDBCUpdated
>>if file("X:\MyApp\AppUpdates\database.zip")
>>   *!* unzip the SDT meta data files and any other
>>   *!* files into the production database folder
>>   erase X:\MyApp\AppUpdates\database.zip
>>   llDBCUpdated = .t.
>>endif
>>if file("X:\MyApp\AppUpdates\UPDATE.FXP")
>>   do X:\MyApp\AppUpdates\UPDATE.FXP
>>   erase X:\MyApp\AppUpdates\UPDATE.FXP
>>endif

>>*!* Then I create the SDT oMeta object and run the validation if needed