I have seen files with 500,000 to over 1,000,000 individuals!  They're
a little slow when you get up into those numbers but Legacy normally
runs fine with that big of a file.

The file size limit is set by Microsoft Access, the database Legacy is
built on, to 2 GB but when you get close, you can start getting some
strange errors that we have no control over.

When you have a large file, running check/repair and compact family
file on a regular basis are even more important to avoid empty spaces
in the database which can slow things down.


Sincerely,
Sherry
Technical Support
Legacy Family Tree


On Mon, Sep 7, 2015 at 9:32 AM, I Macaulay <[email protected]> wrote:
> What would you consider a large file?     Is there a capacity on Legacy?
> My data entry is taking longer and longer.     Also I am getting slower and
> slower.......     Hmmmm
>
> Ian
>
> If at first you don't succeed, then sky diving is not for you.
>
> Ian Macaulay   Carp, Ontario
> Open at 10:AM   Close at 5:00 PM
> 45.2397 N long: 76.0991 W Elv 137 M UTM
>     Don't Forget to Save the Stamps
>
> ________________________________
> From: Michele/Support <[email protected]>
> To: [email protected]
> Sent: Monday, September 7, 2015 7:43 AM
> Subject: RE: [LegacyUG] Error in new version
>
> The clue was “not an index in this table”  The data wasn’t lining up
> correctly.  I always like to think of a check/repair like the Windows
> “defrag” and “chkdsk” (though this might not be the best analogy if you ask
> one of the programmers).  When you are working in your file making
> additions, merges, deletions and imports the data gets “loose.”  (I don’t
> know of a better way to explain this).  When you do a check/repair
> everything gets checked and lined up properly.  Sometimes there will be a
> reference or a link to something that doesn’t exist anymore and the
> check/repair will delete that reference/link.
>
> It is important to do routine check/repairs on your file.  The more you work
> in your file and/or the larger your file is, the more important
> check/repairs are.  I work in my file every day so I check/repair my file
> every day before I backup my file.  If I am entering a lot of data and I am
> going to backup more than once in a day I will check/repair my file before
> every backup.  This might be a bit of overkill but it certainly doesn’t hurt
> anything.
>
> Michele




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/[email protected]/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/[email protected]/

Online technical support: http://support.legacyfamilytree.com

Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our 
blog (http://news.LegacyFamilyTree.com).

To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Reply via email to