Thanks Erik. I figured it had to be something easy! < g >

Bonnie

>>I ran into an interesting dilemma, hopefully I missed something obvious.
>>
>>I was working on an enhancement for a client. This included adding a field to one of their tables in a database, which I had already done on my version of their database in my office. While I was still in the process of working on this, the client called with a problem that I couldn't figure out, so I asked him to zip up his tables and email them to me ... not bothering with the DBC.
>>
>>Well, of course, because of the extra field I had added in my environment, trying to open his tables with my DBC didn't work. No problem, I figured, I'd just open my DBC and modify the table in question and put the DBC back to where it was (getting rid of the extra field), but VFP wouldn't let me. It gave me an error message (which I expected it to do), but then I figured it would let me continue after warning me. Nope! I couldn't figure out any way to modify anything. Is there a programmatic method of doing this? There has to be some way that I overlooked. I didn't look all that hard, to be honest, cuz I had saved my copy of the tables, so I simply copied my table back, made the change in the DBC and then copied the user's table back, so it was not a problem in this situation. However, it could pose a future problem, so I'd like to know what to do if the need ever arises.
>>
>>TIA,
>>Bonnie
>
>VALIDATE DATABASE RECOVER