>I started working on this earlier this year, but haven't worked on it for a while (so many things to do, so little time <s>). However, I plan to get back to it fairly soon.

It would be very cool to merge the forces on this one!

However, I wouldn't like to support another set of database extensions from SDT in addition to xCASE. This makes things even more complicated:
1. Create a model in xCASE
2. Update SDT extensions from xCASE
3. Update DBC from SDT extensions or from xCASE.
When everything can be done in one shot: Update DBC or any other back-end database directly from xCASE model.

Unfortunately, xCASE does not provide a DBCX compliant manager that would allow a VFP application to access these extended DBC attributes directly from the xCASE model. I already wrote my own manager that does that. I just need to write the Validate method (another big task) for it to be 100% DBCX2 compliant.
I don't need it right now because I never update an xCASE model from DBC.

xCASE also does not do very good job when converting VFP models to SQL7 models. it also needs a feature that would allow to synchronize models and not just to export models from one platform to another.

I know that every developer who is doing a multi-back-end application in VFP is facing some of these problems.

It would be nice if SDT can work with the xCASE model or possible other models (ERWin???) directly!!! and use it's own metadata tables only if xCASE or some other tools are not used.

Or.... should I talk to the folks from xCASE instead :)))

Please let me know what people from Stonefield are thinking about all this.