I'm using a trial version of FM2019. I'm importing a large MIF file into a frame document. Each time FM2019 just quits. The MIF file would generate a frame document of 2100 pages. I know this because the same MIF file imports into FM7.1 just fine.Any thoughts?
First off, make sure you're all patched up - just loading FM fresh doesn't mean that you have all the fixes that were added since it was released. Next, have a look at your machine - are you running the 64 or 32 bit version of FM2019? Do you have enough RAM and drive space? Is your FM file local or on a network drive?
I have plenty of drive space and it a local version.
Does it give any message when it chokes on the MIF file? Any errors logged?
No errors. It just quits.
Can you describe the steps of what you're doing? Post#5 seems confusing to me.
I create a MIF file in Visual Basic.It's important to note the MIF file contains NO pagination information or Tag definitions.
I Import that MIF file into a Frame document. (Which has the pagination and Tag definitions). Also in the MIF file is an Include file pointing to a table file.
I think that is important, because this morning I saved a MIF file from a Frame Document and opened the MIF file in FrameMaker and it was fully formatted. So I think it has something to do with the way I'm importing. I'm going to try importing without the include file reference and see if that works.
I hope this makes sense.
Does it make any difference if you just open the MIF file in FM and then save it as a .fm doc (then you can import formats/tags from some other FM doc into it to make it look good)?
I'll try that.
If opening the files, as I suggested yesterday, does not work, I suspect it may be an issue with how the MIF file is generated. I haven't kept track of any changes in the MIF code base, but perhaps something has changed.
I've imported 10 other MIF file (smaller) and they worked fine. But I'm going to compare my MIF file with the one I saved out of Framemaker.
This worked sort of. I opened the MIF file and Imported the formats. Everything worked except the included tables didn't import.
I'm going to try embedding the table formatting next.
re: I create a MIF file in Visual Basic.
What does the header look like? For a MIF7, it should be something like:
<MIFFile 7.00> # Generated by FrameMaker 7.0p578
Otherwise, FM2019 might presume it's an FM8 or later MIF, and misinterpret some characters or markup.
<MIFFile 2019> # 03/28/2019
<MIFFile 7.0> # 03/28/2019
I was going to suggest this but I didn’t know who to send it to.
I will send the MIF file and an empty frame document in a minute.
Sent from my iPhone
Jeff, Thanks for your reply. I'm running 64 bit version on Toshiba Laptop with 16GB of RAM. I just checked and I'm up to date on any updates.
What happens if you open the FM file directly?
It opens just fine. I select-all and delete the existing import. Then import the new MIF file and within a few seconds FM2109 just quits.
You don't usually import the MIF, but open it. After you open it (it gets converted to an FM file), you should be to cut and paste it.
Was the MIF file created in FM 7.1? 7.1 did not support Unicode, so one thing I would watch for is character set problems.
Since you can open the MIF file in 7.1, you might try deleting everything after page 1000 in 7.1 and saving the result as MIF. Can you open the first 1000 pages in FM 2019? If not, what about the first 500 pages? 100? 50? 10? Once you've succeeded in opening a part of the document in the newer version, can you open the following part?