Record locking

[John Esak]

> I saw a similar situation years ago running windows ?? over a lantastic
> network. I believe that I set PFSYNC to ON or ALL in filepro and did
> something to the network also to cause it to write the cache after each
> transaction was saved at the workstation. I could never go back and find
> what it was because it was so long ago but it definitely had to do with
> network and/or windows holding transactions in the cache until forced to
> write them to disk.

> --
> William Akers
> MGM Industries, Inc.
> Hendersonville TN USA
>
> _______________________________________________
I understand what you are saying... and it probably _does_ have to do with
Windows somewhere somehow... but filePro is working with in-memory values...
not those written to disk... so if you say:

      num=ctl(1) and then refer to it later... filePro is using its own copy
in memory of that value... it doesn't matter _when_ it gets written to
disk... it is going to be written in the proper sequential order of
things... or at least that is the way it is supposed to work... :-)

John