🚀 go-pugleaf

In article <ddl683-110892142954@coco2.albany.edu>, ddl683@csc.albany.edu (Dreaming) writes:
> 
> In article <1992Aug11.142806.12760@dartvax.dartmouth.edu>,
> geoffb@coos.dartmouth.edu (Geoff Bronner) wrote:
> > 
> > In <DDL683.92Aug10230338@esther.albany.edu> ddl683@csc.albany.edu (Dreaming) writes:
> > 
> > >A co-worker of mine received a disk with a membership database in
> > >FileMaker Pro format on it.  I have an old copy of FileMaker II which
> > >I never use, but I figured I might be able to translate her file with
> > >it. 
> > [The rest deleted.]
> 
> 
> > Filemaker II can't read Filemaker Pro files, period, end of story.
> [The rest deleted.]
> 
> 
> It's not really the whole story, though.  If you read my original post, I
> mentioned that FMII _was_ able to "recover" the entire database into
> another
> file.  This implies (to me) that it does understand the format in which the
> Pro database was saved, and can make a reasonable go of building it into a
> file.  But it won't _show_ it -- even the recovered file, when opened,
> returns
> the same version number warning.  Frustrating.
> 
> It's really not a big deal.  Thought someone might have hacked out the
> same problem.
> 
>                                             Derek L.

That warning means that it did not read the data in the file.  It attempted to
do so and read part of the file, but not enough of it to be able store the
data.  FM Pro is backwards compatible with FM II in that it can read FM II data
and convert it to FM Pro.  However, it is not compatible the other way; it can
not create a FM II file.

Your best solution is to find someone who has FM Pro, open the file, and export
to a TEXT file.  Then create an empty data base in FM II, and import the text
file.

As always, I speak for myself, and not for my employer.