I'm working on converting a FPW 2.6 app to VFP 9. It is for a company with multiple branches. Each branch has its own set of tables stored in a separate folder. These are all free tables and won't be converted to be part of a DBC. When this setup is used with tables included in a DBC, you can use SDT to create a different DBC for each set of tables, SDT seems to lump all free tables together. This does not pose a problem for many tables, since the tables all have the branch number at the end of the table name, making them unique. However, some tables are seemingly named without the branch number on the end and SDT will not add another version of this same table name to the free tables list, even if it is located in a separate folder. I imagine I can fool SDT into performing an update on such a table (data structure updates being the thing I most commonly use SDT for in the application) by altering the meta data record and "fooling" SDT. But I'm wondering if I'm missing something here and there's a way to get SDT to not lump all the free tables together.

Russell Campbell