The change in the database is not an update in the database engine, just a
change to the schema.
This means Legacy can read an earlier version OK. However the new file
format - added fields and tables - gives the extra functionality required.
Foxy
----Original Message Follows----
From: BE Kelly <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: [LegacyUG] 9 August release
Date: Sun, 14 Aug 2005 17:40:58 -0400
John R. Bayle wrote:
Snip
This is one example of how confusing things have now
become. There are now TWO versions of Release 5.0.
One writes Version 5 files ONLY and the other writes
Version 6 files ONLY. I have often wondered about
Legacy's inability to write out files in earlier versions' formats.
Even FTM does that!
This is a limitation of the Access database. Access does not have the
ability to store data in previous version formats, it can load older
versions but only be converting them to the format of the version doing the
loading. If you want to complain address your concerns to Microsoft not
Millennial.
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
