>I am upgrading a FoxPro 2.6 program to VFP 6.0. The conversion process showed no real glitches, but there is a situation revolving around the following line:
>
>@ 15, 1 GET doresorce FUNCTION "*T" PICTURE "@* EXIT;LIST;STORE"
>
>With the line contained within a DO WHILE loop, if the selection is LIST, a list box pops up as desired, however, when a selection is made and focus returns to the button set, if not enough time has elapsed, pressing any of the keys will redisplay the list box. Doresorce is assigned the value of 0 in the line immediately before this, but clicking on EXIT or STORE will still produce the same result as pressing LIST.
>
>If I let the program set about 4 to 5 seconds after the list box has left the screen, the proper action occurs, but if I click on either sooner, I get the LIST response. I have tried timers to slow things down and let the value of doresorce catch up, but that did not work, and even if it did, it is not a practical approach when the clients are expecting faster running systems.
>
>If I step the the program at this point, everyting works fine, but there is also a sufficient time lag so the problem does not occur.
>
>Any thoughts on this bizarre behavior?

Well, only that IMO, VFP6 conversions should not contain @ SAY or @ GET.

These should be replaced with a standard windows selection dialog.