RM does do a direct import of a FTM data file, but only for versions
of FTM from 2006 or earlier. This is likely because FTM has always
used a proprietary data structure. It used to be possible to save FTM
data in teh format of earlier versions. If that is still available,
try saving as a 2006 version.
>While the windows can be resized the flexibility is less that in FTM
>2012.
>
That comment is just wrong. You need to spend a bit of time with RM,
and if you have a difficult time learing it because of all the
features, buy the book.... it's packed with information that is
difficult to discover by simply playing with the program.
>One of the things that I did not see, that I use a lot was an equivalent
>of an FTM Book. I uses the FTM Books to completely preserve my working
>in a universally readable PDF format. My books include multiple
>genealogy reports, charts, and text document that review my conclusions
>for points supported with a lot of circumstantial data, family
>summaries, and conjecture on the family origins.
>
RM does have a very good book feature. Look under
Reports/Publisher/Create a new book.
Once there you can include charts, narratives, etc all as chapters
with bibliography and index. Once completed you can save it as either
a PDF that will maintain all the links (ie, click on names in the
index to go directly to that location in the book), or save it as an
RTF file whtich can then be edited in Word.
>I did not see any thing like this available in the free RootsMagic, or
>indications that it was available.
>
>Has anyone tried to import FTM data into an MS Access type of database?
> All of the data in the FTM can be outputted in reports. It seems
>these reports could be imported into MS Access tables with the name as
>the key field to the table.
When I used FTM (many years ago) it was possible to generate a custom
report with the data you wanted to include in the Access file, then
save that and import it into Access. I don't recall the details, but I
remember that it was pretty easy to do, because I did it very often.It
may be taht I copy/pasted it into Excel before importing the Excel
file into Access.