Record locking

[Kenneth Brody]

GCC Consulting wrote:
> 
> We all know that after doing a protected lookup using write filename should
> unlock the record to which the lookup was done.

It does.

Well, let me rephrase that...

filePro will tell the O/S to unlock the record.

> System:
> filePro native 5.0.11
> Server Dell with 1GB RAM, mirrored 18K RPM drives, Windows server 2003, network
> 3com Hub 100Mbs.
> Workstations: various make clones all running Windows XP pro 900+ GHz to 2+ GHZ.
[...]
>          then: emm(10)= purchase_order_number+"1";wrtie emm

I am assuming that you typed this in, rather than used cut-and-paste?

[...]
> Changed the line again:
> 15        if:
>          then: emm(10)= purchase_order_number+"1";wrtie emm;sync emm;close emm
> 
> Repeated above steps, this time the record was unlocked right away.

filePro will unlock the record at "WRITE emm" immediately after writing
it.  If adding the CLOSE changes the behavior of the lock, then there is
something wrong with your network.

If you have a case where WRITE does not unlock the record, contact
support and arrange to send them a file to demonstrate.

[...]

Also, if adding a SYNC causes a change in behavior in cases where the
workstation doesn't crash before exiting filePro, then once again, I
would have to say that there is a bug in your network.

-- 

+---------+----------------------------------+-----------------------------+
| Kenneth |     kenbrody at spamcop.net      | "The opinions expressed     |
|    J.   |    http://www.hvcomputer.com     |  herein are not necessarily |
|  Brody  |      http://www.fptech.com       |  those of fP Technologies." |
+---------+----------------------------------+-----------------------------+