>>First off, I have performance worries. Our main database has 73 tables, 222 views, 67 relations, 3127 fields, and 225 indexes. To initially create the SDT metadata and to Validate the metadata takes about 7 minutes (that seems reasonable to me). But what is a bit unreasonable is the time it takes to simply open the SDT Database Explorer -- 5 MINUTES! Every time I need to make a change to an index, view, or table I need to wait 5 minutes? (My machine is a P166 with 64 MB of RAM).
><<
>
>I agree with you on the speed. It is horribly slow. I think it is the treeview control which is reponsible for it. The outline control would be faster. A grid would be fastest!

Yeah, the explorer sure is nice once it comes up though, I have to say that...

I bet you are right...the loading of the explorer as well as the semi-validation it does beforehand must combine to make it take long for these larger databases.

It would be nice if one could open the explorer for a specific table, like "modi struc" allows in the conventional way. I suppose that might have some downside though as far as handling all the dependencies when a field gets changed. Once the explorer is loaded in its entirety it probably makes it easier for the program to update all dependencies when fields change, etc.

I am babbling now, so I will shut up. I have to go test my Reindexer. Took me about 5 hours to code. If anyone would like a lightweight reindexer application that generically handles reindexing VFP database-contained tables without keeping additional metadata around, let me know. It seems to work pretty well so far.

Thanks for the response...

JoeK