Hi Carl...

I will neither confirm or deny as it may or may not violate one of many NDA's with MS that I have signed. However, I think it is safe to say that MS has more than enough technical capabilities to fix the issue. IMO - I think it is more of a business issue. 3 revs of Visual FoxPro have gone to market since the last version of FPW 2.x shipped - which would be March of 1994. In Internet Time - that is an eternity. I for one can see both sides of the coin. One one front - I can see how it can set a dangerous precedent. Since when has it been a requirement that software developed 5+years ago - be 100% foward compatible with today's hardware an operating systems. How about the close button in FPW 2.x in Windows 95/98/NT 4? Should MS fix that as well? Where does one draw the line. I for one - don't care. In fact, I would much rather have the Fox team work on new features than worrying about the forward compatibility of FPW 2.x. IMO, FPW is a dead product.

Does this point of view make me customer unfriendly? Maybe it does. Then again, I tend to take a very pragmatic point of view with these type of issues. IMO, the SlowStart solution works fine - at least it has for me.

Finally, just to disclaim everything - my views are my own. I do not work for MS - nor do I make the claim of representing MS in an official capacity. Rather, the purpose of post with regard to patches is 100% from the point of view of being a SYSOP on UT.

>On CompuServe, Brad Schulz said that, based on a conversation he had with an >MS rep at a conference, MS is working on a legitimate update to FPW to handle >the fast Pentium problem.

>Can anyone confirm or deny this?