Nine years. It's a number - I don't know what to do with it. Any questions the community might be considering should weigh the benefits of MS being the primary (or almost only) xBase custodian. Maybe it's good - maybe not so good. There are still alot of things we are not allowed to do. Could someone else could do it better (or at least as well)? I sure feel bad when the newspeak tends to portray the xBase community as "out of touch welfare orphans".

I don't want to feel that my preferences are causing MS any problems.

BTW - have you seen those screen shots links in the "sexy marketable" thread. It's amazing what some are doing with your baby! Total refresh! If you know of any additional links - please - by all means pop them in.

Thanks.

But there is no need to even consider that since VFP 9.0 is available today and is supported through 2014. So even if we stopped evolving VFP today (which are not), VFP 9.0 will be around for almost 10 more years. On top of that, the recent survey showed that 42% of all VFP developers world wide still maintain apps using VFP 6.0, and support for VFP 6.0 was dropped years ago.
>
>We will be doing far more than a service pack for VFP in the coming years, but it may not be a traditional upgrade. Also, our focus will be on leveraging .NET technologies and having VFP work well and take advantage of new products and technologies.