Installed OS 10.1.2 and when I launched the OS 9 native version of FMPro v5.5 instead of it opening it classic, it just crashes.

I then installed the OS X native version and all was fine. However, like most intelligent sys admins, after I experimented for exposure, I went back to OS 9.

Now when I double-click a FMPro db on my desktop, it produces a bogus error about incorrect installation, missing system components and insufficient memory. If I launch FMPro and do a File:Open, no problems.

Obviously the OS X version is causing the OS 9 version to misbehave. Anyone know if this is a known issue or am I special and will have to deal with it accordingly?

I deleted the X version and association under v9 is working now. Would still like to know if you must have both versions installed in order to move between OS versions and if these two problems are known.

I think what's happening is when you have both versions on your computer and are booted into 9, when you double-click a FMP file, it tries to open the file with the X version. I work most of the time in X, but when I do work in 9 I get around this problem by dragging and dropping the files to an alias of the 9 version of FMP.

Chuck

I too have been doing the File:Open solution. Below is the word from FM, Inc.,:

Here's the deal: FileMaker Pro 5.5 for OS 8/9 was not designed to run in

classic mode under OS X. It was not tested or certified for this, and it is

not recommended.

If this customer wants to use FileMaker when booted into either OS on the

same machine, he should install FMP twice. Install the OS X version when

booted under OS X, and the OS 8/9 version when booted under OS 9. To avoid

the file association problem he is reporting, I recommend launching the FMP

application first, then using the Open command to open the desired database.

This is the general feeling I am getting from companies about Classic support, it is most unfortunate.