Mike:

>I don't mean to be rude, just a little fed up. :-)

OK. I see where you're coming from here. You know what, I think your probably right.

I have used Fox since '89. I am using VFP7 now, I don't have a need for it, there is a showstopping bug that needed a workaround to run some very robust VFP6 production code of mine. Why am I using it then? Well its nicer, the devenv is better and there are some really usefull additions/upgrades to the language. Nowadays, I actually feel that there is something wrong when I use VFP6 coz it aint giving me the accurate language syntax as I type <s>.

However, if the existing community aint using the latest and greatest version of Fox, this has to speak volumes to MS. Your right, its not about the revenue that upgrades will generate for MS, IMHO its about whether its actually worth going on with developing VFP. If they cant get the VFP community to upgrade, how can you expect them to sell to new users and therefore whats the point - they may as well just go into maintenance mode for VFP and discountinue support in due course. I think thats what failure to upgrade says to MS. Period.

Nevertheless, you can actually see a lot of Fox die-hards actually talking .Net all of the time now. It seems that .Net is the VFP upgrade path. Makes me a little fed up too coz I am very happy with the Fox, my framework and the tools I am very productive with right now.

I think expecting any great steps with VFP is pissing in the wind. Maybe, we just have to accept that notion (I nearly said fact). However, if MS give VFP enough to keep playing in the sandbox and compatible with OS upgrades, that is surely better than nothing?

Best

-=Gary