Recover File then FM Unexpectedly Quits

[cbr400rr]

Been using 5.5 with OSX & 512 on a titanium. Been incredibly successful for about a month then all of a sudden my favorite file claims to be damaged and suggests I use recover to open it.

I use recover which runs fine and save it on the desktop and but when I go to open it Filemaker unexpectedly quits everytime. I never get to even open the file...any ideas?

Chris

[LiveOak]

You might try opening it on a Mac running another OS. Otherwise, how is your backup situation?

-bd

[Texarado]

I, too, am having this problem. FM Pro 5.5 on a G4 using OS-X 10.1.5. Ditto on my G3 using the same system and software.

I can open the file on my G3 Powerbook, which is running OS-9. No problem there.

I had to export the data from the OS-9 system, then import it into a backup file in OS-X.

This seems to be a serious problem, yet there is not mention of it on the FM website.

[kenneth2k1]

Yes, I recently was burned also, but it was on Win98/2k machines. It was suggested to me that there may be an error on one of the layouts. Do you get a type 2, 3 or 11 error (well, i guess you probably wouldnt get those on OS10) Backing up everyday is key

Ken

[Raschelle]

I've had this problem too. Running 9.2.2 and FMD 6.04. Yesterday the file was fine, today it's damaged and I recovered it. Now FMD quits with the type 2 error. An interesting thing I noticed about the memory. The more I assign to it, the more it seems to use (according to the About this Mac window). At 10 mb, it was using 9.9, so I set it to 50 mb and it now uses 48.8. What's with that?!

Well, at least I should have a good backup on one of my tapes.

[falkaholic]

Yup. I've had this happen a few times in the past year. Also had FM Server for OSX totally mess one to the point of being unrecoverable.