Freechain question

[Don Coleman]

List:

Ken posted a response several weeks ago stating that it was not required to
have all users exit a file before rebuilding a freechain.  He stated fP
effectively locked down anyone trying to add or delete records while the
freechain was running (if I remember correctly, certainly not his wording).
Over the past week I had two freechain rebuilds occur as a result of running
an archive process while other users were one the system and in this file.
The archive process copies the appropriate records from the source file to a
mirror destination file, then deletes the record in the source file.
Typically, if I am going to have a freechain rebuild occur it is when I turn
two interfaces (one an ascii import, one a socket connect) back on after
running the archive process.  If I run the archive process while these two
interfaces are left on I will surely get a freechain rebuild, so I turn them
off.  This lessens the odds to less than 50%.

Now to my question.  This AM I turned one of the interfaces back on and it
posted 10-20 records and then the "rebuilding qs1 freechain" popped up on
the interface window.  I exited the application and then immediately started
it again.  No freechain error has popped back up, the interface is still
posting its data and has been doing so for about 75 minutes.  If fP
automatically detects a files' freechain needs to be rebuilt why didn't it
pop up when I re-started the interface the second time?  There are
100,000-200,000 records in this file and if I manually run freechain it will
take approx. 60 seconds to complete.  When the interface was re-started I
can't believe it completely rebuilt the freechain since I closed the
interface displaying the freechain with 2-3 seconds of it appearing.

Windows 2000 Advanced Server, Windows 2000 & WINXP Pro. Clients, fP v5.0.13.

Don Coleman
Donald G. Coleman, Consultant
402 Andrew Circle
Indiana, PA 15701
dcoleman at dgcreact.com
(724) 349-6302