>>Problems with indexes was one of the first things that I tackled back when I wrote my first framework in FPD 2.0. What I did was to create a table for each system that stored the necessary information to re-build all index tags for each table in the system.
>>
>>This thread has reminded me that VFP's DBC stores information that I'll need to access for some systems. Thanks, Mark.
>
>I did the very same thing in the simpler FP 2.x days. But with all the stuff in the DBC, it was cheaper to get Stonefield than to develop my own time (which is $$$ to me). Plus you get other valuable functions with SDT as well. Plus I got a 10% discount being a Premier UT member.


I put together a routine using bits and pieces of gendbc.prg that receives a tablename as a parameter, and does the same thing as gendbc, but for one table only, and you don't need exclusive access to the dbc to use it. After running the program on a table, you have a code listing that will recreate the table's structure including indexes and extended information (pk etc.) We have begun using this program as a tool to act as a backup during development as well as to make sure that data structures between test and real data are consistent. You can run the program on a table, switch dbcs, run the output program, and you have just copied an extended table structure from one dbc to another. Extremely useful. I also put together version for views. I will upload them both to the files section today, they are called 'gentable.prg' and 'genview.prg'.