Record locking

[Bill Akers]

Kenneth Brody wrote:
> Bill Akers wrote:
> [...]
> 
>>As I insinuated earlier, there were three potential users working
>>simultaneously and all of them could have had the same number since the
>>network/windows was holding the changes in cache rather than immediately
>>writing back to the files on the station that was acting as server as
>>soon as one station had asked for a new number.
> 
> 
> Then the cache was broken.
> 
> 
>>There was enough lag
>>that even after a ticket was written and printed and stored, you could
>>not always find it in the system from another workstation until the
>>filepro session was terminated, in which case the information was always
>>updated and the new information was stored.
> 
> 
> Then the cache was "very broken"[tm].
>

I concluded that at the time but just had to find a way to force it to 
flush. Waiting for either Microsoft or the Lantastic folks to come out 
with a solution was not an option at that time. A Novell tech actually 
told us what to do to the network or windows whichever it was because he 
had run into a similar situation on a Novell network somewhere with 
another app(I don't know whether he mentioned what it was).


-- 
William Akers
MGM Industries, Inc.
Hendersonville TN USA