>Hiya Fred ---
>
>When VFP5 came out, I began a personal moratorium on FP2.6 development and the fast CPU problem (and others) is the nail in the coffin.
>
>IMHO, implementing a solution in 2.6 nowadays is doing a disservice to your clients. You are proposing technology which is dated and rapidly losing official and unofficial support. The only possible reason would be if the client is running a Win3.1 shop and refuses to upgrade. Even in that case I'd be leary and probably refuse the "honor" because I wouldn't want to buy into developing and supporting an app on an old topology.
>
>

John:
Everyone has to set their own limits. I agree that FPW 2.6 is hitting a barrier due to faster CPU's and I point this out to clients who have newer equipment or are purchasing newer equipment. But I have clients with PC's that are 75~166 Mhz (Y2K compatible) and they will not be upgrading for 2~3 years because of accounting practices. Some industries cannot afford to be continuely upgrading and only change operating systems or PCs when there are problems that cannot be solved by the existing technology. I have to keep a PC with Windows 3.1 to test my software on.

My view point is that if I do my best to support them now, in 18 months when the clients begin to plan their upgrades, I will get the call to rewrite or upgrade their software. Who knows what we FoxPro will be like in 18 months?