>>>>Here is some code derived from legacy code. The TIMEOUT clause does not cause a time out after the specified number of seconds. Is this a known bug?
>>>
>>>I'd lean toward it is not a bug per se, but incompatibility between legacy code (@ SAY/GET w/ READ CYCLE) and more current style of coding introduced with Visual FoxPro (OO-style form objects and READ EVENTS). Might be easier to simply redo the forms (often the underlying logic can be adapted -- in some cases it is simplified), than it would to try to apply various workarounds and have to deal with "quirky" behavior as a result..
>>
>>VFP is downward compatible, isn't it?! It's either a bug or a quirck or by design. My best hunch is that it started to be a quirck with the introduction of faster computers than at the time it was implemented.
>
>check this.
>
http://support.microsoft.com/kb/133739/en-usThe TIMEOUT clause was not the topic in that article.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
