Peaceful coexistence of FM 8 and 10

[mandrill22]

Is this possible? I just opened FM 10 for the first time and and it crashes every time I open an existing document.

[Arnis_Gubins]

I've got FM6-FM10 on the same platform and they all get along.

What's your OS, default printer, etc.?

[mandrill22]

Windows XP Professional Version 2002 with SP3. I must add that the first few files I opened were crash recovery files and since then I have been able to open some other files without crashing. So it appears the problem may be file-related and not a conflict between FM versions. I may have panicked too soon. If I want to leave files compatible for FM8 users, what is my best "save as type" option?

[Arnis_Gubins · Accepted solution]

You can save as document 10.0, 9.0 or 8.0 binary (.fm)  or 10.0 or 7.0 MIF version from FM10, so save try saving as FM 8.0 binary.

[mandrill22]

Thanks! That works.

[Van Kurtz]

You can save as document 10.0, 9.0 or 8.0 binary (.fm)  or 10.0 or 7.0 MIF version from FM10, so save try saving as FM 8.0 binary.

I have a trial copy of version 10, and the save as shows only 10 and 9 as the binary save options, NOT 8. Is this true, or the trial version limited?

[Arnis_Gubins]

Van,

This is what I see in the FM10 pre-release version. I can't say what is in the trail version. What's the trial p value, i.e. FM 10.0pxxx?

[Jeff_Coatsworth]

I've got the release version (10.0.0.388) & it doesn't show FM8 as a Save As .fm version.

[Van Kurtz]

Arnis,

For what it is worth, the trial version I have is 10.0.0.388, the same as Jeff's release version. If your version is pre-release, Adobe must have decided to remove the feature.

[Arnis_Gubins]

This was in the p375 version. Makes me wonder what else was dropped or shuffled around for the final release.

[mandrill22]

I thought this issue had been resolved through some earlier discussions with Arnis but I have some new issues with FM 10 to 8 compatibility.

As some of the earlier posts point out, the only FM8 compatible document format that may be used when saving an FM10 document is a MIF 7.0. Such a document will open with FM8 but with problems. Mainly, anchored frames will resize (granted it's a difference of thousands of an inch but this is enough to make some frames pop out and go into next available columns). The more serious problem is that some referenced graphics are replaced by gray boxes--not because of incorrect linking, but because of filter problems. Even if you delete the graphic (gray box) and try to reimport it in the FM8 version you get a "filter encountered an error, cannot complete the translation" error.

The graphics in this case are vanilla JPEGs, nothing special about them as far as I can see. I even opened the graphics (originally created in Photoshop) in a different program and saved again thinking the problem may be with the JPEG file itself. No change in behavior...still get the filter error for some graphics.

Has anyone had any experiences similar to the ones described above? Any suggestions?

FM8 V 8.0p277

FM10.0.0.388

XP SP3

[Art_Campbell1]

Have you tried the less elegant approach of simply saving as 10 MIF and opening that in 8?

If it works as it should, 8 will simply parse and discard what 9 & 10 features it doesn't recognize.

To me, it seems less prolematic than saving from 10 > 7 and opening with 8...

Art

[mandrill22]

Hi Art,

Yes I did try opening MIF 10.0 with FM8 as well but got the same results: missing graphics, anchored frames popped out etc.. The curious thing is that if I delete a referenced JPEG (which is properly displayed) and then attempt to import it...I can't import it! I get the same filter error message.

Also don't understand why width of frames in the MIF are in ten thousandths ( e.g. <BRect  0.0" 0.00151" 4.84999" 2.62999"> when this has been defined in Object properties as 4.850 X 2.630 ) while object properties rounds up to one thousandth of an inch. This may explain the frame resizing behavior due to rounding up...I am guessing. I have pretty tight tolerance for imported graphics using nested frames (anchored frame inside a text frame) and sometimes I simply turn on Gravity to size the height of the graphics frame. This possibly creates a frame with a height of, say 2.84167 but the MIF file when opened in FM8 adds 0.00033 (to round up to 2.842) which is enough to displace the anchored frame.

Just trying to rationalize the resizing problem. Stumped as far the filter problem goes.

[Shubhankar334229324xw5]

• I faced the same issue, Save the document as FM 8.0 binary. It will resolve automatically.