importing to a clone - file smaller than original

[Stephen S]

I've created a simple new database for a project at work. Its is about 940 kb.

At home I have a copy of the file to tweak and improve it, by adding new fields (not changing the old ones). I create a clone of the file at home (no records) then import the work file. All works fine. Same record numbers and pages in Preview Mode etc but the file is smaller - 788kb. Why. I'm worried something was overlooked. It is tedious trying to physically compare the 600 records for differences.

[Stephen S]

Just figured something out. A cloned file is smaller than the file with all the records deleted. What is missing?

Stephen

[SteveB]

FM deletes fields that you may have previously deleted, and compacts indexes. Don't worry, be happy.

Steve

[Stephen S]

Thanks

So as a principle should preferably stay with cloning to keep the file as "clean" as possible?

[Fenton]

If you want it to be completely empty, cloning is the way to go. However, it also wipes out any globals, so if you keep little graphics or colors in global containers, those will be gone. With 7 it would probably be better to store such graphics in a single record table anyway.

Alternatively, if you Delete All Records, then Save a Copy As [ Compacted Copy ], the resulting file will be very near to the size of the clone. If you have FileMaker Developer there is a File Maintenance command which can do this to the active file in one step. Very convenient; not scriptable however (I imagine 'cause FileMaker Pro doesn't have that command at all).