Hi Jonathan
> Silence...
>
> Interesting.
>
> You do all know there is a serious bug in FMP 10 that can cause file
> corruption, don't you? I have a client that got hit by it. FileMaker
> knows about it and is planning on an update soon. I was not involved
> in the conversations with FMI, though, and do not know the whole
> story.
>
> I thought someone mentioned something here related to it recently. I
> was just curious if there was any more information about it "in the
> wild."
I hope I don't get shot down in flames here, and I know your knowledge
of FileMaker is much greater than mine, but my understanding was that
the error is in Recover.
I thought it was just reporting an error when there isn't one. Is it
actually causing the corruption it then reports on, in the original
file, rather than the recovered one? If so, then it's a very good
example of the reason why never to go forward with a recovered file in
any circumstances. (I speak as one who has been burned!)
FMDiff doesn't seem to think that there is an error in the original
file, with the ones I've tried it with.
Whether or not the error is real or imagined, this situation has
caused me to be a lot more disciplined with my development, and take
many more backups, sometimes several in one day. Every cloud has a
silver lining, as they say!
None of this means I'm not keen on FMI releasing a fix!
Colm
_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au