FileMaker in OS X won't run any files!

[Nik]

FileMaker was running fine for a while with Mac OS X, but suddenly it has stopped working. I've not been able to think of anything which might have triggered the change.

The symptoms are that it will launch and open files, but when it displays the file's window it gets as far as drawing the window border, title bar and white content-background, but then stops and sits with a spinning rainbow cursor forever (or at least half an hour before force-quitting FileMaker). All we can get is empty windows with spinning cursors.

We've re-installed FileMaker from scratch with no luck. The same files open fine on other machines with the same version of the OS and FileMaker.

Has anyone else seen this, or got any ideas?

Setup: FileMaker Pro 5.5 on a G4 Mac with Mac OS X 10.1.2

[spragueg]

I am having the same problem. The only thing I can do is reboot. It works for a while and then dies.

I started having a problem with copying text from classic apps and pasting into X apps at about the same time. I have no idea if the problems are related.

[Corys]

The copying and pasting between classic Apps and OSX apps is a known problem which hopefully should be fixed with 10.1.3.

as far as your FMP files opening, I was having some problems similar, and it turned out to be some bad fonts in my layouts.

are you using any non standard fonts?

[Nik]

Nope. The only fonts used in the files are Times New Roman and Arial. And the problem occurs for any files.

We've since re-installed Mac OS X and it now works again

*fingers crossed*

[spragueg]

Figured it out. If you have Classic set to launch when you login it causes a problem with the pasteboard and apparently FileMaker. I set classic to launch when I open a classic app. Copy/paste between X and classic works fine now. It also seems to have fixed filemaker too. I get no more spinning rainbow and white screen when open a file.

[spragueg]

Well, the problem just popped up again. It's been just over a month since I last saw it. Not starting classic on login seemed keep the error from happening until today.

Do any of you have a better solution?