Craig,

If I had to hazard a guess, here's what I think we may see (or might hope for).

>Not in any order, here are some of my wishes:

>- Better ADO support, primarily the ability to bind all controls to a recordset.

Yes, yes, yes. I'd hope so.

>- OOP menus

Dubious. Here's how I feel. First, menus are pretty much application specific, so what would we gain? Second, the LIFO stack implementation of VFP menus is a very powerful construct already. Third, and perhaps most telling, menus aren't even objects in VC++, they're resources.

>- More editor enhancements. I'd like to see multiple clipboards, ability to split the editor into multiple windows so I can view two or more sections of the same prg/method at the same time. Abilility to seach mulitple objects in a directory.

I'd say so. Look what we've seen so far with VFP 7.0's beta.

>- Better documentation. Improve the examples in the help file. Look at SQL SELECT. The syntax has changed dramatically since Fox2x, but the examples haven't.

I think we'd all like better docs.< s >

>- Callbacks and increased COM support.

Highly doubtful on the former. VFP's internal memory management currently prohibits it. I don't know how big a deal it would be to re-write, but the guess here is major. Not that that would make it prohibitive. Afterall, look what happened to VB (or was going to). The concern here would be the performance impact. IOW, does VFP's current memory management contribute to its performance? If so, don't want it or need it.

As far as "...increased COM support", in what areas?