Gregory,

all what I say that a

select 1
replace ...

will not be interupted if autoyield is false.

A simple REPLACE without is nothing that I would use except the simplest test routine

Agnes


>Hi Agnes aus Berlin,
>
>What I'm saying is that certain 'things' can change the selected workarea. eg clicking in a grid changes the work area to the grid's recordSource
>
>It doesn't have to be a 'sequence' of lines - the replace can be on (in) a command button
>
>Even with autoyield off, certain commands force the processing of window events (eg a mouse click) - DoEvents is one of them (not sure about inkey(), but I bet it does)
>
>I remember putting DoEvents somewhere in my code - and when the user typed/clicked too fast - the program went crazy
>
>I'm not saying you have had problems - but ommitting the IN can - one day - give a problem, that may be hard to debug and/or reproduce
>
>Like I said
>>>Better safe than sorry
>
>
>
>>Hi Gregory,
>>
>>I'm not sure about timer events - but one should not use it anyway. <g>
>>A code sequence SELECT REPLACE in subsequent lines should not create IDLE. At least thats the sence of autoyield=.F.
>>
>>I never had problems here, and I do a lot coding inside grids.
>>For what I remember there where problems with IN and the current workarea at EOF too. I'm not shure if this is solved in some version.
>>
>>Agnes
>>>>
>>>> _VFP.AutoYield = .F. and nothing will trouble exeqution sequnece. ::)
>>>>
>>>>Agnes
>>>
>>>
>>>Not really, Agnes
>>>
>>>Timers, DoEvents, Foxpro deciding it has an idle state (which processes pending windows events like mouse clicks) may change the current work area
>>>You may have a programming error
>>>
>>>Better safe than sorry