Try opening in access

Carrie

-----Original Message-----
From: LegacyUserGroup [mailto:[email protected]] On 
Behalf Of Billy Mittelstadt Jr
Sent: 19 July 2017 19:54
To: [email protected]
Subject: Re: [LegacyUG] Locked out of Legacy

Is there a way run check/repair without going thru the program? Just can't get 
to program due to error screen.

On July 19, 2017, at 2:30 PM, JV Leavitt <[email protected]> wrote:

Close Legacy, and open it again. That might be all you need to do, but if you 
still have trouble, run file maintenance.  The RIN numbers that should be gone 
after a merge in Legacy will stay active, but get removed when you close the 
program and open it again.  If this isn't in the to-do bug list, I think it 
should be.

Joseph Leavitt


On 7/19/2017 9:06 AM, Billy Mittelstadt Jr wrote:
> Did a manual merge of individual, and got message can't find individual ID 
> 44475 (this was not the record numbers of either ID). And then Error Checking 
> for shared events. Error 3021: No current record. When hitting user prompt 
> "YES" for try again get endless loop. When hitting "NO" prompt, back to 
> individual ID 44475 not found and message Run-time-error 440: No current 
> record. How do I get Legacy back?
> If I do have to revert back to backup file, is there a way to restore sources 
> to SourceWriter format?
>
> Thanks for your help.
> Bill


-- 

LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/
-- 

LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/

-- 

LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/

Reply via email to