>OK, that works. However, I would suggest to add a PARAMETERS or LPARAMETERS statement. If no parameter is provided, the program should ask for the table name.

That is an idea, thanks.

>Somewhere, some basic validation should be done that important values are not missing, especially the field width. When adding an additional field, without the field width, my entire table got deleted! Of course, I was working on test data.

Okay I'll check this out and put in tsome validations.

>Also, when adding an additional field (this time, with a valid field width), I notice that the entire data gets erased - the program only maintains the structure. The VFP built-in commands, ALTER TABLE and MODIFY STRUCTURE, do the equivalent of an APPEND FROM - no data is lost.

I'll work somthing out, right now it is a simple delete and recreation.

>Losing the data may be acceptable under certain conditions. For instance, in Bata-Bolivia, I did all my changes on a copy of the database which was empty anyway. Then, I had a special program that updated the official version (the shared database), at midnight (basically, copying the entire empty database, and doing an APPEND FROM for each table).
>
>In general, however, I believe that maintaining existing data will be a requirement for any MODIFY STRUCTURE substitute.

I agree with this completely

Glad you liked it in general and this newer version now maintains indexes for modi stru.