Problem with FileMaker Pro version 2.0v2 on a CAP volume

Article View: comp.protocols.appletalk

Article #3994

Back to comp.protocols.appletalk Previous Next

#3994

From: Rob Tanner
Date: Fri, 08 Jan 1993 22:54

32 lines
1536 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

Technical Details

Message-ID: <1993Jan8.225458.24150@leland.Stanford.EDU>

Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!nntp.Stanford.EDU!rob

Show Full Headers

Complete Article Headers

Newsgroups: comp.protocols.appletalk
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!nntp.Stanford.EDU!rob
From: rob@leland.Stanford.EDU (Rob Tanner)
Subject: Problem with FileMaker Pro version 2.0v2 on a CAP volume
Message-ID: <1993Jan8.225458.24150@leland.Stanford.EDU>
Keywords: CAP FileMaker
Sender: news@leland.Stanford.EDU (Mr News)
Reply-To: "Rob Tanner" <rob@sherlock.stanford.edu>
Organization: Stanford University, California
Distribution: na
Date: Fri, 8 Jan 93 22:54:58 GMT
Lines: 32