FileMaker Pro Advanced 11.0v3 on Mac OS 10.6.6. 

Created clone of database. Ran consistency check on the clone. Got 
message to the effect that the privilege sets are damaged or have been 
tampered with. 

Canceled the check. 

Opened the Clone file, using Full Access account, then closed the clone. 

Ran consistency check again, it reported no problems found. 

Repeated this with several different databases, got the same behavior. 
Also did it after quitting FileMaker and after restarting the computer. 

Also created a compressed copy of the database and checked its 
consistency before opening it. No problems reported. This oddity seems 
to affect only the Clone of a database. 

What gives? Should I be worried about the integrity of the Clone file? 
Is it perhaps some characteristic in the creation of a clone file, that 
produces this consistency check error if the clone file has not been 
opened?

-- 
Bill Collins