>Hi all,
>
>My company finally decided to cut support for our customers still running in FoxPro DOS and UNIX and offer them our "windows" version (for a complete background please see thread 606882).
>
>Now I need to write a nice and kind letter explaining them why we are doing this and how this is going to be for their advantage...
>I found already the "product support discountinuance" list in MS site but I need more ammunition.
>
>There is any documentation out there on the benefits of going to actualized technology, the importance of keeping current, the perils of being stuck in the past or something like that?

Aside from the obvious issue of FPW no longer being a supported product, and as a 16 bit application, unable to take advantages of things like long files names, ActiveX and COM support, and the existing list of known issues that will never be addressed, there are questions as to how long the product will be able to run on front-line hardware and software. The product does not adhere to the Windows standard for UI behavior, installation and cross-product integration. There are internal behaviors that you have to carefully code around, and a wide range of things which you'll never be able to take advantage of in the Win 16 environment.

Add to that things like the speedy processor kludge,a diminishing pool of talent that can support and enhance the application, and a number of system problems which can only be addressed by adhering to the standards of DOS/Win16, and it's pretty obvious that as people upgrade their systems, they're going to stub their toes more and more.

I'm not even discussing the assortment of features available in VFP that just aren't there for FPW.