I don't neccessarily buy into the premise that just because MS is not currently putting a patch out for FPW - they don't support the product as I think they are two separate things. After all - if you call for technical support - you will get it. Heck, they still sell copies of FPW. Upgrading the product - which is what a patch essentially is - is not the same as supporting. Besides, other alternatives exist. Finally, three versions of VFP have shipped since FPW last shipped in 1994. In my opinion, MS shipping a patch sets a bad precedent. Does this mean that if a problem is encountered with Excel 95 on a 600 mhz machine - MS should patch that because folks don't upgrade. With three versions of VFP out there covering 3+years - more than ample time has passed for folks to upgrade. If people won't upgrade - the SlowStart solution is out there. Once again, I have some FPW apps out there - and SlowStart works for me. If a viable alternative was not there - I could see the issue. People have accepted the fact that the Close Box in FPW does not work. Nobody has ever demanded MS patch that. And for that issue - there is no workaround or third-party solution.

My final point - if you continue to work with 4+ year old software that has been rev'd 3 times since it releases - you then accept the risks. There are companies out there who don't support versions more than 2 revs old.

As I see it, there are 3 legitamate solutions:

1. Upgrade the client to 32-bit if you can
2. If you must stay in 16-bit OS - try to upgrade to VFP 3.0
3. If 1 or 2 is not acceptable, use SlowStart

Happy New Year :)