I have been using filemaker pro 5.5 for OSX for some time with no problems. Suddenly, whenever I start the program is simply quits half way through the installation process. I have tried reinstalling to no avail. What is going on?

Try throwing out the FileMaker plist found in your Users>username>Library>Preferences folder. This will more than likely correct the problem. If this doesn't help, please reply and we'll try something else.

Thanks so much, that did the trick.

I have a somewhat similar problem.

I was called in to fix a problem. Not my original client. using latest OSX on G4 tower and Filemaker 5.5v2. to host (not server servion). Only 1 file and not many records. This file only accessed by two Mac OSx clients.

Same machine is also hosting another very small filemaker file via web sharing plug in. They are sharing access to that database over LAN with Mac and Window web browsers.

Problem is that database keeps getting corrupted. I went in and figured that they had system folder sharing and filemaker sharing both on and probably contention conflict. So I move files to non shared foolder and everything was working perfectly when I left.

Now they tell me filemaker data file is getting corrupted again. What gives?

Any ideas appreciated.

I have the same problem.

Called Tech Support (Used my single 'free' phonecall.)

He advised me to export my 3,500 records to tab-text format,

reconstruct my layouts from scratch in a new database,

then import my tab-text records.

It took me almost a week to create the original file.

Before I took his advise - I tried to open one of the filemaker pro templates provided on the CD with the application - GOT THE SAME ERROR:

"Filemaker Pro has unexpectedly quit."

I guess I now have to pay a fee to call him back and tell him that his advise doesn't work!

I tried trashing the plist as suggested in another reply to your message - didn't help.

Anybody getting a handle on this problem?

Thx

Dan Hopper

iMac 500

384meg RAM

OSX 1.4

Same problem just cropped up for me today. I cloned the file from the OS 9 version of Filemaker 5.5; the clone still gave the error on OS X FMP 5.5. I also tried deleting the .plist, and that didn't help; I reinstalled Filemaker from the CD; that didn't help; tried to update to 5.5v2 (my cd is 5.5v1) that didn't help. In fact, when I tried to update, the update failed with some cryptic error message. It seemed like the installation progress indicator had just got to something about Info-macos.plist (which is a file inside the application package, right?) when it failed. I had to trash the Filemaker folder and start over from the CD, then the updater. Then I tried opening my file again with the freshly updated 5.5v2; still no go. THEN I updated to 10.1.5 (from 10.1.4) and it still doesn't work.

Strangely, my database consists of about 12 files, and only one of them causes FMP to give the unexpected quit. The file opens fine in 5.5 under OS 9. Fortunately it's the simplest of all the files, so it won't be too hard to rebuild it.

Interestingly, the problem showed up right after the file had to be recovered after an unrelated crash.

I sure hope someone figures this out, but I suspect that nothing will happen until the next (v3?) release, whenever that comes...

"Interestingly, the problem showed up right after the file had to be recovered after an unrelated crash."

Coincidence? I don't think so.

The recover command is only intended to fix the corrupted database enough to extract the data, not to completely repair the file (otherwise it'd be called the "Uncorrupt" or "Repair" command -- FileMaker Inc choose their words carefully).

Open the last backup you made before the crash, clone the appropriate file and import the recovered data into it. Don't forget to re-set autoentered serial numbers in the define fields.

You did backup, didn't you?

I also have a problem with FMPro under OS X 10.1.5.

I used the programme without problem under 10.1.4. Then I installed the 10.1.5 Update and now the FMPro programme won't start any more.

It just quits silently.

Any ideas?

I will try the plist trick later.