>>
>>Yep - send out the metadata, run the Update method of the SDT classes, and it builds the whole thing there from scratch. better, it builds them with the right paths, and if you create >1 each in it's own folder, each references the right tables.
>
>But the coremeta must be very very different from the demo version or the data is stored in another place.

SDT creates and registers some SDT-specific extensions through DBCX; check with the people at Stonefield if you need details. Doug's done a great job with it, and I suspect that you simply aren't aware of what it can do. It's not just random garbage that tries to shoehorn stuff in the wrong way. DBCX is there because it's an extensible standard that fits neatly with other DBCX-compliant extensions; CodeBook-derived frameworks and products coexist nicely with SDT...

I had all kinds of code that I was able to retire thanks to SDT, and it did things I wish I'd thought of, or if I had, I'd determined that the cost of implementing and testing them adequately made them expensive to roll on my own. Like I said, YMMV, but so far it's done everything I expected and more.