Ken:

I am a big fan of yours. I still use genscrnx and PTX in legacy 2.6 systems I have developed and still maintain. So my following comments are hard to direct at a "hero" of mine :(

>Its not like VFP is a version 1.0 product with issues preventing its usage and deployment, rather it is extremely mature and robust.

I bought VFP5, VFP6 and I also bought the VFP7 upgrade and am developing with it - well, I say developing, I am editing, coding and creating in VFP7, excluding the VFP new/enhanced features. I use Intellisense, bookmarks and the task list when I am developing. However, I still deploy in VFP6. Why? My application will not run correctly in VFP7 - period.

Just one aspect of what my application does (Outlook Automation) prevents me from using VFP7. When I try to move a message from the Outlook "In" Box to another Folder when I use the collection's Move method causes an OLE dispatch error. I would point out that this is longstanding, bug-free, trouble free code that has worked fine with VFP6 for some considerable time. That one thing alone means I can't use VFP7 "in the field", so to speak. There are other issues like this that have cropped up here that cause similar problems for other developers. What to MS is a VFP bug and has been agreed and "passed up the line" can be an absolute show-stopper for a VFP developer's application.

Yup, I have upgraded to VFP7. I never got involved in the beta and never wanted to. I wanted to wait for the bug-free version so I did. I bought it and I use it but I can't deploy it.

I for one am desperate for VFP7 SP1. So, whether VFP7 is "extremely mature and robust", it does not work for me at this point in time. For this reason alone, I remain disappointed that I can't use the product as advertised and I still can't use the new language enhancements that I have paid for because they will not work in VFP6 - the most stable runtime for my applications in the field.

This is a real silly situation.