>>
>>I heard about this last year!!! This is really strage, but some engineer at MS suggested putting in delays (like a DO WHILE with a millisecond delay) throughout the application if it detects a faster machine. Sounds bizarre, but it's true. Apparrently, there is some element of parallel processing that is much more (too?) efficient on the faster machines so that certain computations will fail. (I think it's I/O related, but I'm not entirely sure.) It doesn't make a whole lot of sense to me, but that's what MS said.
>>
>>This was a topic last spring on the foxpro-L mail list. Does anybody else remember this?
>
>Hi Matt,
> Yeah, MS told us to "slow down" the application too. Here we are trying to get the applications to run faster and MS tells us to slow them down. :-). I would like to see a better interim solution to this until the application can be rewritten in VFP. But, what's going to happen to all the FPW application still running out there when people move to faster machines and all the applications start breaking?
>
>Bill


Is is possible to issue a system level command to slow down the system? Like a half-speed command to make a 200 perform at 100mHz temporarily. It would be like telling the system to perform a calculation every OTHER iteration. If so, maybe this could be issued from a PIF or similar type file prior to opening FPW.

I can't believe that FPW is the only language/app type that can/will be hit with this kind of issue.