I've run into a problem at a client site.

It seems that VFP5 occasionally runs ahead of itself. It occurs most often when calling specific methods or DODEFAULT()'s. If a property of a form is set in the method, the line of code after the method runs with the old property value.

Something like:

thisform.lMyProperty = .F.
thisform.myMethod()
IF thisform.lMyProperty
WAIT WINDOW 'Property is True'
ENDIF

myMethod() Method:
...
(Code)
...
thisform.lMyProperty = .T.
...
(More Code)
...
RETURN

The WAIT WINDOW sometimes fires. If I run the code with the TRACE window open, it always works (of course! <g>).

I'm not sure if it matters, but the clients are running on very fast (Pentium II 400) PC's.

Anyone else seeing oddball behavior like this? Any Idea what will happen to similar code on the inevitable Pentium 800's which will be coming into fashion a few years down the road?

- George [Perplexed]