> How is the class then instantiated, in the form's .Init()?

We don't actually use forms, the data is loaded via the business object, but basically you would have a member object built into your form classes that specifies the name of the data environment to instantiate. Because it's actually built into the form class, it'll be instantiated before any other controls.

> I think I mentioned that our shop is currently using ProMatrix and it would take more than custom DE's to get folks to switch.

Actually, no, you didn't mention that you were using ProMatrix. I really didn't post this to try to sell you VFE, I was just pointing out that we'd done it, so therefore, it's possible.

After we release out 6.0 version we'll be offering a competitive upgrade which will provide a plethora of reasons to switch. We've really done a great deal of work from our 5.0 version to this one and there will be a tremendous number of unique features in VFE that will make it worth your while, especially if you're doing n-tier applications as well as large or highly complex applications.

> From everything I've read using the native DE is faster in opening files and
setting relations because "the DE uses low level file operations".

I'm not sure where you read that, but it's not true. When the DE opens a table it uses the same underyling technology that the USE command issues.

What you do get with native DE's & cursor classes is poor error handling capabilities, zero re-use, a loss of flexibility (that you've already described), and duplication of effort. :)