Filemaker 7 Developer keeps crashing

[AJB_UMASS]

I just patched my Macintosh to OS X 10.3.9 this morning, and now FM 7 Developer refuses to run. Every time I try and launch it, it 'exits unexpectedly'. Anyone else seeing this behavior?

[stanley]

AJB:

I patched to 10.3.9 last night, and FMD7 works fine for me this morning. You may want to search through the Forums and see if you can find similar behavior from before 10.3.9 - I know some people were having problems with unexpected quits or refusal to launch, but I can't remember what the solution was. Chances are, it is some cache or other that needs to be cleared on the OS level.

-Stanley

[AJB_UMASS]

Hmm. Well, a quick search for 'quit', 'crash' and 'launch' comes up empty. I'll keep looking, however. Thanks for the tip.

[AJB_UMASS]

OK - problem was solved, but it involved re-applying an earlier Apple patch. Specifically, re-applying Security Update 2005-002; this replaces the Java libs with an older version. Once I did this, FM7 Dev. worked properly again.

[Fenton]

I saw, at http://www.macsurfer.com an acknowledgement by Apple of the problem; and what you did was the work-around.

I'm holding off on 10.3.9, waiting for a 10.3.9.1 (if such a thing is even possible, 10.3.9 was supposed to the last, but hopefully they'll do a minor revision to fix this problem; I have no idea).

[Tony O]

Patched fine for me. However, having learned the hard way, with every update I fix permissions before and after. I also recently discovered Applejack (Thanks MacFixit!), which is shell script that you can use in single user mode at startup to perform maintenance tasks. I love it. It's GPL, so I'm attaching for anyone who cares to give it a spin.

Tony

AppleJack-1.3.2.dmg.zip

[artypants]

FileMaker 7 Developer crashes intermittently on both Mac OS X 3.9 and on Win XP SP2. I have been anoyed by the fact that all development is lost since the last disk save. But today I decided to run the recover tool on the file to ensure there wasn't any corruption being introduced. FileMaker crashed during the recover operation. Now the ORIGINAL file is corrupt beyond repair. It now asks for password when there is no password. I spent $45 on a service call to FileMaker and all they could say was that for $100 per table, they would look into it. My solution has 9 tables and I'm putting this thing together for a non-profit at $50 an hour. I should have gone PHP/MySQL.