Also, when you delete a record, an empty space is left in the middle of the
file where that record was.  Filemaker has some internal trigger to decide
there is enough empty space to 'clean' the file to fill in those empty
spaces.

I'd guess that Filemaker Server doesn't do any 'cleaning', it just opens the
files.  So every time you test a backup with regular Filemaker Pro, it's
doing the same 'cleaning' process.

An interesting test would be to shut down Filemaker Server, open ebase with
Filemaker Pro, then close it (it should 'clean' during the close).  Then
re-open with Filemaker Server. Test a backup again and see if it 'cleans'.

- Bob

-----------------------------------------------------------
Bob LeLievre
LeLievre Information Services
List Management Services for Non-Profits
voice:  617-474-9131
email:  [EMAIL PROTECTED]
website:  www.lelievre.net


-----Original Message-----
From: Walter Daniels [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 25, 2002 10:15 PM
To: TechRocks Support
Subject: [support] RE: FMPro 'cleaning up unused blocks'


It is akin to what Access does. All text fields are variable length (up to
65K), so if you change an address or similar changes to records, it is
likely to have to write the new version at the end leaving a hole which can
get compacted. The internal data structure of FMP files is not publically
documented so the above is just a guess from lots of experience implementing
databases. It may be dumb enough that any change, even one for which there
is room, gets moved to the end.
-----Original Message-----
From: Eric Johnson [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 25, 2002 9:19 PM
To: TechRocks Support
Subject: [support] FMPro 'cleaning up unused blocks'


The last few times I've test-unzipped & test-used one of our ebase archives
on an isolated machine, it's taken FMPro a couple of minutes to close out of
names_.102 when I quit -- and while it waits, it displays a message about
"cleaning up unused blocks".  On the network, we use FMPro Server 5, but I
frequently test the archives to make sure the zipfiles/ebase data aren't
corrupt.

Is the "cleaning unused blocks" message about a process of cleaning out
ghost records, perhaps?  Akin to compacting a database in Access?

Trouble is, I don't know anything about us eliminating tons of names_.102
data in the recent past.

Does anyone know specifically what FMPro is doing in this instance?

Thanks for any info you may have to offer.

Regards,

Eric Johnson
CEC
Eric Johnson
Colorado Environmental Coalition
1536 Wynkoop #5C
Denver, CO 80202

Keep up with CEC news & goings-on at
http://www.ourcolorado.org

------------------ Reminder to each recipient: To change your list account
preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support
and enter the email address you used to subscribe to the ebase support
list:: [EMAIL PROTECTED] To unsubscribe send a blank email to
[EMAIL PROTECTED] ---------------------------------------
------------------------------ ebase - Relationship Management for
Nonprofits,
http://www.ebase.org -------------------------------------------------------
--------------
------------------ Reminder to each recipient: To change your list account
preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support
and enter the email address you used to subscribe to the ebase support
list:: [EMAIL PROTECTED] To unsubscribe send a blank email to
[EMAIL PROTECTED] ---------------------------------------
------------------------------ ebase - Relationship Management for
Nonprofits,
http://www.ebase.org -------------------------------------------------------
--------------


------------------ 
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support  and enter the email address 
you used to subscribe to the ebase support list:: [email protected]

To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
 ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------

Reply via email to