>>Another thing you might want to look at is the GenDBC program in the Tools\GenBDC under your main VFP directory. This will automatically allow you to programatically generate the DBC and it's views. The code it produces can be used and modified to fit your particular situation.
>
>Hey George,
>
>I just checked it out... Am I understanding correctly that I can, once I'm relatively satisfied with my database structure, store the generated code in my application and then just modify it and resend just the EXE as needed? Updating tables, views, data, etc.? Without disrupting the client data? That would be way too cool...
>
>Renoir

That is partially correct with GenDBC. You have to take only the code you need to make CHANGES and run it at the client's site. However, any CREATE TABLE will need to be changed to ALTER TABLE. Otherwise, no data is saved if you [re-]CREATE TABLE.

Do yourself a favor, save yourself time and numerous hours in billing time, and get SDT. It will more than pay for itself in the amount of time you save rolling your own procedure. SDT will do all this for you at the client sites using the DBC/DBC/DCT files of your database and the SDT metadata.