>>To add to Marks suggestion. What I've done is write a prg that opens the database exclusively and issues the appropriate ALTER TABLE commands. Add the prg to a project and create an EXE to take to the client. Run the EXE to change the tables on the clients machine and then copy your new EXE upgrade to the machine.
>>
>>>My users wanted some upgrades made to a vfp EXE I coded for them. The upgrade included some field length changes in some of the tables. The tables are in a Database. Is there a way I can append the old Database to the new upgraded Database so my users can retain their old data?
>---
>Hi Colin .. that sounds good.
>My first EXE could be upgrade_tables.EXE. This is will run the ALTER TABLE command. Then I could code in the first part of my upgrand_program.EXE.. vali database... do I need to code vali database?

No. Since you are actually doing the work within the DBC it shouldn't need to be validated later. Another thing I just thought of is if your DBC contains views based on tables that have been changed don't forget to include code in your upgrade_tables to recreate these views.