Joseph,
Yes, I had tried all of that before I brought it up here and sent the email to
support. Most of their suggestions seem to be based on the problem being with
the fdb file. I don't think that's the case with mine because it does it with
every file even the sample.fdb. But my laptop
Using Build 364, Check/Repair works okay for me. I see some verbiage
about error 91 on the Legacy Help Center pages:
http://support.legacyfamilytree.com/category/11/0/10/Error-Messages-Problems/
Joseph Leavitt
On 12/14/2013 8:36 PM, Dave wrote:
> Jim,
>
> The latest build (364) corrected my prob
Jim,
The latest build (364) corrected my problem exporting to a new Legacy file as
well as to a gedcom and back to a new Legacy file. That all works with no
errors now. But I still get an immediate error 91 when trying to run a
Check/Repair on any of those files.I even get error 91 when
This is a known problem with importing a GEDCOM in build 361.
Brian
Customer Support
Millennia Corporation
br...@legacyfamilytree.com
http://www.LegacyFamilyTree.com
On 13/12/2013 6:50 PM, Brian wrote:
> I just tried to save a Gedcom and got an error 3021 also.
> Went through the process of cre
Jim,
Exporting all records to a new Legacy file gets an error 3021.
Exporting to a Gedcom file goes OK.Re-importing that Gedcom goes fine until
it starts creating the Family File and then stops with an error 3021.
Dave Pointer
Try the export st
I just tried to save a Gedcom and got an error 3021 also.
Went through the process of creation with no problems, 3021 displayed
after trying to open it.
Any suggestions?
Thanks,
Brian
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 2
And I'm getting error 3021 when I am trying to SAVE an event.
Mary
On Fri, Dec 13, 2013 at 12:51 PM, Dave wrote:
> Richard, it isn’t just you.I’ve experienced similar problem (error
> 3021). Also, I can’t run a check/repair without an immediate error 91,
> I think it is. I tried a
Try the export steps.
Original Message
> From: "Dave"
> Sent: December-13-13 2:10 PM
> To: LegacyUserGroup@LegacyUsers.com
> Subject: RE: [LegacyUG] Export to new Legacy family file, error or bug?
>
> Jim,
>
> All went ok with the List Cl
Jim,
All went ok with the List Cleanup.But when I try the Check Repair, I get an
error 91 immediately.
Thanks
Dave Pointer
--
Dave,
I have helped other with this problem. I have done a number of things to fix
the persistent error 3021 abd error 91
uot;
> > Sent: December-13-13 12:52 PM
> > To: LegacyUserGroup@LegacyUsers.com
> > Subject: RE: [LegacyUG] Export to new Legacy family file, error or bug?
> >
> > Richard, it isn't just you.I've experienced similar problem (error
> 3021). Also, I can
Yes I can confirm this is a new problem.
From: Richard Van Wasshnova [mailto:rfvanwasshn...@gmail.com]
Sent: Friday, December 13, 2013 2:01 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: [LegacyUG] Export to new Legacy family file, error or bug?
When I try to export to Legacy family file eit
> Subject: RE: [LegacyUG] Export to new Legacy family file, error or bug?
>
> Richard, it isn't just you.I've experienced similar problem (error 3021).
> Also, I can't run a check/repair without an immediate error 91, I think
> it is. I tried a few things from
Richard, it isn’t just you.I’ve experienced similar problem (error 3021).
Also, I can’t run a check/repair without an immediate error 91, I think it
is. I tried a few things from the support page with no luck. I sent an
email to support but haven’t heard back yet.
The strange t
Richard,
I think you mean IMPORT a Gedcom.
This is a known problem with Build 361 that
should be fixed in the next update. I believe it
is related to the database conversion that took place.
john.
At 03:00 PM 12/13/2013, Richard Van Wasshnova wrote:
>When I try to export to Legacy family file
14 matches
Mail list logo
