I guess doing GOTO RECNO() will also write the change. And in my case it is far simpler because I need not redo the rlock.
>Flush, Unlock, Record. Why I used these words?
>
>I have a record locked (RLOCK). There's no buffering scheme.
>I change a Logical field using a checkbox with the Controlsource set to the field, but I do not leave the record.
>I press a button that starts a new EXE that uses the same record.
>It must use the changed value, but it didn't.
>
>So I tried FLUSH before calling the new EXE. Didn't help.
>So I tried FLUSH FORCE before calling the new EXE. Didn't help.
>So I tried UNLOCK before calling the new EXE. This did help.
>
>This does not make sense to me. Hackfox tells me that FLUSH
empties all internal buffers of data (which have nothing to do with record or table buffering) to be written to disk. How does this match with what I read in the original Help which says:
You can use FLUSH to explicitly save to disk all changes that you make to all open tables and indexes.?
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.
