Problem with FileMaker Pro version 2.0v2 on a CAP volume

Thread View: comp.sys.mac.databases

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Rob Tanner Mon, 11 Jan 1993 05:30

#609

Author: Rob Tanner
Date: Mon, 11 Jan 1993 05:30

31 lines
1534 bytes

I have an on-going (meaning I haven't been able to fix it yet) with
FileMaker Pro version 2.0 (both 2.0v1 and 2.0v2) files becoming
damaged (and sometimes NOT recoverable) when residing on a CAP volume.
I have not had the same problem with files residing on the Mac.

Is there some parameter, et cetera, I need to be aware of in building
CAP (I'm using 6.0pl100 and about to upgrade to 60pl126)?  Has anybody
seen a similar problem.  It is intermittent.  The user may go for
several days with no problem and then try to open the file and get the
message: 

           This file was not closed properly. Filemaker
           is now performing a consistency check

Followed immediately by:
 
           Sorry, this file is badly damaged. Please use
           the recover command.

I'd appreciate any help I can get with this problem.

Thanks,

Rob Tanner
Stanford University

-- 
Rob Tanner                              Internet: rob@sherlock.stanford.edu
System Administrator
Stanford University, California

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads