----- Original Message ----- From: "Kevin R. Phillips" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Sunday, August 14, 2005 2:49 PM Subject: RE: [LegacyUG] 9 August release
> John, > > Legacy (and at least two other desktop vendors that come to mind) routinely > upgrade their databases within major releases. They do this because they > are adding new features but want to get them to the user without having to > wait or go through the pain of creating a new "major" release. In the case > of Legacy this is true at least back to Version 3 (which is where I started > using Legacy) so this isn't anything new. Neither Legacy or the others > allow selecting which database version you want to use when you open the > database, it prompts the user to upgrade the database to the latest that the > version of the program current supports. Trying to maintain code > compatability with more than one database version would add a huge amount of > complexity to the program so I don't fault them for not trying it. > > Since Legacy (and the other vendors) provide these updates for free, the > assumption is that when sharing a database with another at a different > update level, that the person at the lower level will update their program > to the current level. > > In this case, and I certainly don't speak for Millennia, I believe their > intent is to allow people who do not immediately upgrade to version 6 the > ability to still share databases with people who do. This is a courtesy to > the users so they don't feel "forced" into going to the new version just > because someone else they share data with happened to do so. (So you could > argue that they might actually LOSE money since they aren't forcing their > customers to convert immediately) > > It is true that the new features in the database (the "Version 6" database > format) can't be viewed or edited with Version 5 so some of the data that is > shared can't be seen by the V5 user. However (and knowing the changes in > the database), this won't cause any corruption issues, they merely won't be > able to see that data. (For example, the new DNA feature) > > Kevin > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John R. > Bayle > Sent: Sunday, August 14, 2005 4:04 PM > To: [email protected] > Subject: Re: [LegacyUG] 9 August release > > Jon Raymond wrote and asked... > > > If we download the August 9 build now, what effects, if any, will > > that > have > > for using v5? Should we wait for v6 to be formally released? > > It means your files are no longer compatible with other users of Version 5 > (such as myself) who have not yet upgraded! > So you are now compatible with yourself, other upgraders, and users of V6 > such as those who were at the BYU conference. > > I can send you my data and you can read it. But you cannot now send your > data to me unless you use GEDCOM. Or you could persuade me to upgrade to > the most recent version of Version 5.0. > So you now have a Version 5 which is not fully compatible with Version 5! > But you are compatible with some BYU conference attendees. > > Seems to me that what the Millennia folks are calling 5.0.0.256 would be > better called 5.1.0.2 or something. Or maybe even Version 6.0.0.2. Because > it cannot write 5.0.0.0 files, it is wrong to call it 5.0.anything. On the > other hand, maybe I'm wrong and it does write 5.0.0.0 files. > jr > > > > 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 > 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
