>I've been asked by our DBA (an Oracle person) to review SDT as a possible tool for our modular app project. I know SDT is a really cool tool to have, but I need to find out ramifications related to licensing and cost... So if we want to use SDT on a multi-developer project, how necessary is it for every developer to have their own copy? TIA!

I also use SDT with local and remote [VFP & Oracle] views. The new version allows you to specify indexes for views. So if you use their OpenTable() method, SDT will recreate these indexes for the view and default the index to what you specify. It also includes functions for recreating indexes based on meta data. So, if you lose all your indexes and info, you can rely on the SDT data to recreate them. Another function, is for repairing damaged tables.

In general, SDT is installed locally (C drive), but the meta data tables are kept in the same directory as by DBC (which is usually on a server). This way, you can launch SDT from any computer that has SDT installed on it. It will default to using the tables of the currently selected DB. If no DB is open, it will prompt you for the DB to open.

There is a field repository where you can define fields to use in tables. When you design a table, you can select a field from the repository. If you change a field def in the repository, you can propagate the change to all the tables that have that field.

SDT also has reports to print documentation for all your tables and views, detailed or summary.