Record locking

[GCC Consulting]

Ken,

1. Error in typing

2. This was a subjective test.  I was running this test while working on the
server.  No network.

3. As I stated, I was running 2 sessions - 1 doing order entry and 1 while
sitting on emm_mast record 1
   
4. Before I send this program to fp support, I will test it on my system 
	server PII 350Mhz running server2000 with 384MB of memory
	Workstation Dell 933 Mhz PIII 256Mb Ram Win XP Pro
	filepro 1.0.13 ODBC

   Over my network I am not having a problem with the code as originally written
with just the write
   Tested the program on my laptop and had no problem

This begs the question,

	a. "Is this a problem with Windows 2003 server?
	b.  The Speed of the drives? 
	c.  Processor speed
	d. all of the above

Since there was no network wiring involved, I don't think this is a network
problem.

Unless fp tech has my client's particular hardware, i.e. server, I don't think
they can duplicate the problem.  I can't on my systems.

Ken, I didn't think this was an fp problem as a close cleared up the problem.  

Richard Kreiss
GCC Consulting 

-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at bestweb.net] 
Sent: Wednesday, March 31, 2004 10:32 AM
To: gcc at optonline.net
Cc: Filepro 2 List
Subject: Re: Record locking

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." |
+---------+----------------------------------+-----------------------------+