>>http://venussoftop.tripod.com/Bhavbhuti/
>
>OK, I am starting to look at it. First suggestion: On your Web page, it should state clearly that it is related to Visual FoxPro - and perhaps, applicable versions. I mean, somebody may accidentally stumble on your page (perhaps, as a result of a Google search), and have no idea what it is about.

Okay coming up next <g>.

>
>Next, I get an error message, due to the fact that the path of the FMT file is hard-coded. This might be defined as a constant at the beginning, but perhaps it is preferable if the path is omitted completely (the developer may need to have the folder in the search path anyway, to use it frequently).

Updated logic.

>
>After correcting this (I took out the path information, for a quick test): Much better than the "cut-and-paste" possibility I find the fact that I can see the complete specification of the field, including caption and comment, in a table view, without having to go to each individual field.

That was the basic idea. I had similar fields many sets and I couldn't remember the properties and had a tought time finding the older fields and duplicating the stuff.

>
>I have a suggestion for default fields. You may want to add two more default fields for a new table: code and description. At least, most of my tables require this. A client table, for instance, would require:

>1) The sequential number (which you provide);
>2) It would not require the key to the parent table; this particular table would have no parent, but many other tables would require the parent key;
>3) A client code - this is the code the user sees;
>4) The client name (I usually use the full name in a single field).

Provided a Hook program file for modifications, so the main PRG need not be modified.

>When running the program for a second time after I got some error message the first time (due to the missing "data" folder, in my initial test)

Data folder user maintained and modifiable in the UI which will be remembered.

I got an error message, stating that the table was already part of the database. However, the file that already existed was "temp1", and not the table I created.

Bug fixed for table deletion

>I get a message "...TempCreateTable.prg already exists, overwrite it?" This can be corrected with SET SAFETY, or making sure the temporary table is erased. Once again, this is probably due to errors in the previous run.

SET SAFETY implemented

>After several tries, I finally managed to create a table - anyway, it does look promosing.

Thanks