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 ---------------------------------------------------------------------

Reply via email to