Re: FileMaker ARGH!!!!
Re: FileMaker ARGH!!!!
- Subject: Re: FileMaker ARGH!!!!
- From: Devon and Cornwall <email@hidden>
- Date: Tue, 20 Mar 2001 17:40:58 -0800
At 7:42 AM -0500 3/20/01, Xandra Lee wrote:
>
I fear that you're correct and that the problem DOES indicate some
>
corruption in at least one of the DB's. Meaning it's time to do a total
>
rewrite.
>
>
RANT: As I said initially, ARGH!!! Since FMP4 It's rare I can even finish
>
creating a moderately complex solution before some corruption enters.
>
(I've never been lucky enough to have FMPs eternally wimpy "Recover"
>
function find the source of the problem.) Suppose I should count myself
>
lucky that the DB still opens.
At 12:56 PM -0800 3/20/01, David Graham wrote:
>
I totally agree with this statement. I had one project where
>
all-of-a-sudden I could no longer create a record with data, but
>
instead had to make the new record and set each cell one-by-one. At
>
one point a recover actually worked, and then it stopped again.
>
FM is definitely not my best friend right now. ;-)
I recall a discussion about file corruption on one of the FMP lists a
few years ago.
The salient points were, in order of importance:
1. Never ever, ever, nohow, backup FileMaker files with the Finder or
any other utility that copies the file. Always save backups from
within FileMaker only*.
2. Do a recover on your perfectly fine DBs *before using FMP to do a
"Save a Copy As" - that one corrupt bit you don't know about may get
fixed rather than propagated to sicken further.
3.This has worked just fine for me for a long time. (well, that
part wasn't actually in the discussion ; ) )
Devon