>Hi again Craig ---
>
>>Yup. It is a separate tool. How successfully you can use that designer with each tool varies. It works better with VB than VFP because VFP doesn't play as well with ADO...but this will change. I'll publically state right now that in VFP 7.0, you'll see MUCH better ADO support. No one told me this...just a hunch.
>
>I happen to like the new DataEnvironment object in VS6. It is a natural assumption that it'll grow into VFP in future versions. And VFP *has* to better support ADO in future versions...even if it takes a complete revamp of the source to accomodate it. Hell, when you think about it, there's no real problem longterm if you supplant VFP's native db with a VS DE call....it'd be another paradigm shift but we're used to them :-)

I would be surprised if VFP Version.Next does not support the VS Data Environment.