>>Hi All ---
>>
>>Maybe this is way premature, but I was reading the other day how Visual Studio 7 is in development for the year 2000 and 8 is in the planning stages. Sooo....anyone happen to know or surmise if versions 7 and 8 of VFP are in that loop?
>
>HA! If they could get 6.0 working I would be happy for a few years.
>
>Things like...
>
>***********
>COM Objects that don't block to single use.

This is already working in the lab. Look for a fix in the next SP.


>***********
>More VFP like access of ADO... perhaps ADO Views or such.. would be nice to...
>create view MyView type ado as select blah blah...
>Then I could do...
>oX = createobject('SomeDataManipulationClass')
>oX.CleanData(MyView) <<--- ado object would be passed

It's a sure bet that this will be improved in 7.0


>***********
>Stop the crashes.. I get kicked out of VFP 6-12 times a day... 2 or so times a day NT crashes... this only happens when using VFP heavily.

Very likely your environment. I'm not having these problems and thousands of other users aren't either.

>***********
>How about a view designer that works and allows complex views?

I doubt you'll see this.

>***********
>ActiveX support... I can't belive the KB tells you to go into VB to create a wrapper to use in your VFP...

ActiveX support will get better, but you won't be able to create ActiveX controls.

>***********
>Support for ActiveX controls that support contanership, like the Cool Bar Control...

See above

>***********
>
>I am sure there are alot of other stupid little things in 6.0 that should be fixed, before they spend anytime on 7.0. If you ask me, the whole team should be working on VFP 6.1 which is a free update, included all above, plus any other needed fixes.

Too late...they were already working on 7.0 even before 6.0 was released. This parallel development is common.

>
>Heck, Id even pay $20 bucks for it to offset shipping the new CD.
>
>Then we can talk about 7.0 and 8.0!!!
>
>BOb