|
|
|||||
 Introducing PTWin32 |
At least they don’t
give you an option for Failure any
more. But that’s small consolation when you can’t change a record. If you’re on a
network and you have a bunch of people working on PTWin32 at the same time
you’re bound to run into a Record Lock sooner or later. A Record Lock occurs
when you try to edit a record that is already being edited by another PTWin32
user on the network. When you open a
record for editing in PTWin32 the system creates a temporary file on the network
with a file name extension of .LCK. This LCK file keeps track of the record(s)
you are currently editing. If another user attempts to edit the record(s) you
are working on the system checks all of the LCK files to see if any other user
already has the record under edit. If it is found that the record is already
open then the other user sees a Record Lock warning and access is denied. When you finish
editing the record and move on the LCK file is deleted or updated to reflect
your new activity. If while editing a
record you crash out of PTWin32, say through a power failure, it is possible
that a LCK file or two are left on the network hard drive. If the system
doesn’t have enough time or power to delete the LCK files then it remains to
report a false open record.
|
||||
 |
|||||
