>So I guess that just leaves the multi-developer issues...since we probably aren't going to get approval to buy three more copies of SDT, the other guys will be using MODI STRUC, etc. That means that when I gather everything to build the meta-data and all, I will have to do a validate on the whole shebang, or else have them itemize their changes so I can run a validate method on the specific database objects. We'll have to see...
>
>Thanks for the response!

Well... if the productivity savings is there... a copy of SDT for each devloper is small percentage of the budget.

What you may want to do is hold off on creating the meta data in the early parts of the project. Once the design stabalizes and there aren't alot of changes appoint one person as a DBA. He will be the person that modifies the data and meta data from that point on. This is the person that will have a copy of SDT. Each developer can email or whatever project communications method you have (email, tracked, etc.) database changes to the DBA... He will make them and publish an updated data and meta data once a week perhaps.

If other developers need to modify the meta data and can't wait for the DBA, they will have to do it with browse.

But, now, what about using the SDT functions. If you are using the functions to open tables and views to get the auto indexing and such, you still need a license for each developer.

>Joe Kaufman

BOb