>Picked up a copy of "Using Visual Studio" by Que from a friend who got it at VBITS. Large book. Looked for Visual FoxPro reference. Found ONE on Page 14: "Visual FoxPro is not included in this book because it is a standalone database and cannot be used to create CPM components". This is not an exact quote but close enough.
>
>Grrrrrrr. Doesn't anybody ever check these books for technical accuracy? As long as these types of "expert" books are published, VFP will never find a solid place in the world.

John,

It is "technically accurate", ask Microsoft they will tell you not to use VFP. The Fox marketing team might as well be dead and fox is next. We need to stop moaning and stop using M$ products, Fox is great but M$ is doing nothing to attract any new developers or businesses to Fox. We should take a hint and all learn something different.

I don't mean to grind the ax the wrong way. I'm just as upset about the slow demise of VFP as everyone else here. But I can quote MS reps telling clients that they should not look to VFP for long term solutions. All the fox people say this isn't true, but I've heard it and you can call Robert Green all you want but NOTHING is changing (what has changed since VFP 3.0 when the rumors began...) VFP has the quietest roll outs of any MS product, doubt if Tahoe will even make a peep. VFP will remain a small MS product for independent developers, corporate America will never buy it without a HUGE push from MS and the VB team....Never going to happen !

Personally I have begun to do all new development in VB and cancelled devcon to use the dollars to catch up on it. In the end we are loosing a great product that was cheap and easier to maintain for small to intermediate systems.

Sunset approaches...

Robert Horkay