>> 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.

Must have been one of my other desperate pleas for help :)

> 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.

Goccha.

>> 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.

I've been trying to find it Mike, but to this point I haven't been able to
do so. It does occur to me though that the trade off in speed might be well
worth the control gained from using one's own DE class.

>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. :)

With features like that, why would you use anything else? :-)

Do you think that your graphical UI will be (could be) a
stand-alone product? It sounds like just what I'm looking for.
Without it, I'm thinking that I'd use the standard DE for it's
graphical capabilities and then hack out a quickie utility to
pull only the information I need into my custom DE class.

I would like more info on you 6.0 product. What's the URL?

...kt