AREV/OI Coordinated Locking (OpenInsight Specific)
At 01 SEP 1999 03:03:50PM Mark Glicksman wrote:
I came across a document titled "Coordinating Locking Using Byte Range Drivers", describing setting RevLockFile in OI to \AREV\REVBOOT to coordinate locking between AREV and OI. Will this same technique work for a non-networked installtion where AREV and OI are both installed on the same PC?
glicks@compuserve.com
BG-Map Botanical Garden Mapping System [img]http://www.libertynet.org/bgmap/bgmap.gif[/img]
At 05 SEP 1999 10:16PM Steve Smith wrote:
I may well be wrong, but I believe that the non-networking driver does not issue locking calls to the operating system. On this basis there will be no record locking. It would be easy enough to test.
If both systems used a common network driver (for a specific network ie. NOT non-networking) with a user limit of one, then locking calls could be sustained.
Steve