Bob,

>First, I would say, once you open the SDT tool, why do you close it again? Just keep it open your whole session.

Just out of habit...I like keeping a clean work area...generally close something when I am done with it for the immediate time, but there is no really good reason...

>Perhaps when you run your app, it closes it... so here is a thought:
>
>I haven't tried this myself, but perhaps it could work. What if you build sdt.app into an .EXE and run it and keep it up on your machine in the background. That way, you wouldn't have to open and close it. Or, you could run a second instance of VFP with SDT loaded and keep it up in the background.
>
>Doug, think this would work. I am not sure if SDT opens the database exclusively or not. (Not for multiple developers but to run SDT and you AP at the same time.)

I am sure it would work, especially just keeping a separate copy of VFP open. Then only the occasional system crash would take it out. One thing which might be troublesome is checking files in and out of VSS. If the files are open at all, VSS takes issue. Yes, we do check our database structures in, as well as the script generated by GenDBCX...metafiles would have to be checked in as well I suppose...

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!

Joe Kaufman