I keep popping back to this forum in the hope that someone is able to post a solution to this very frustrating and potentially damaging situation. I work at ULTRALAB, a learning technology research lab where we use and have used Filemaker extensively for many web delivered projects. I feel very despondant wth using Filemaker at all now - it just isn't stable yet I continue to plug it's versatility as a web database platform that allows rapid prototyping and development to take place.
I am running FM 5.5 Unlimited. In OS X 10.2.6, filemaker unexpectedly quits several times a day. I have even written an AppleScript which checks to see if Filemaker is running (every minute), if it isn't, it launches the FM application and opens all the databases. This works a treat until you discover a corrupt database which needs recovering (happens once every 3 days)
The project involves 400 people and the database receives over 1000 page requests a day. I am confident that Filemaker can support this activity - it isn't that much in the scheme of things.
In desperation, I have tried many options. I have now moved the databases to an OS 9.2.2 machine. Filemaker now runs for a day and a half without crashing (same no of hits) but it still crashes!
Something to note is that once upon a time I did have Filemaker running reliably for months and months using OS X 10.1.5 - not sure why. When I upgraded it all went belly up.
I have been in contact with the technical team at Filemaker. They suggest using uncorrupt copies of the databases - as someone said, it's daft cos the databases will just corrupt again.
They mentioned the technical people are aware and are writing a patch - somehow i don't believe it - it has been too long already.
Any thoughts would be appreciated....