I'm not going to get into a discussion about the "Fox is dead" issue. All I was saying is that the book is not technically accurate: It says you can't do COM or ActiveX in Visual FoxPro, the truth is that you can.

The rest of your post is a whole 'nother (albeit entertaining and worthy of speculation) thread.

>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