Ed, Could you install a version 5 Legacy that still uses the old underlying database structure, then merge the incoming file with your file, then convert it into the v6 database structure and return this newly merged copy back to your collaborator for them to work with again? Would this put you both back on the same page, so to speak? I'm not certain, but wonder if, since the database structure has changed, your collaborator will have to update to Legacy 6 or you will need to stay with 5?
Maybe Sherry, Ken, or Dave will soon drop in with some helpful suggestions for you. Do you still have a valid copy of your old v5 database? You may have already told us; if so, I've forgotten and do apologize. I can imagine how worried you are. Mary ----- Original Message ----- From: "Ed Barnard" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Sunday, September 11, 2005 1:31 PM Subject: [LegacyUG] Intellishare fails on 6.0 and V5-latest. | This problem is the showstopper for me, rendering Legacy 100% unusable | by myself. | | I reported this to Millenia three weeks ago, immediately after upgrading | to V5-latest and converting to the new database format. I received | acknowledgement of the problem report, but haven't received confirmation | or denial that Millenia can reproduce the problem. I've been patient; | they ARE busy with the V6 release. | | I have now installed V6 and the same problem manifests itself with | precisely the same symptom. As a result, we can no longer collaborate. | My genealogy partner has the one and only copy of the Legacy database. I | dare not update my copy. | | The problem is this: | | When importing the other copy of the same database, and proceeding to | Intellishare Merge with Intellipass, the merge spits out scores or | hundreds of spurious changes. Changes are flagged in the Notes fields | (notes, research notes, medical notes) when nothing has changed. The | first couple of times through, not realizing what was being done to me, | I trashed some of our hard-earned research data. I don't care to take | that risk again. | | Two demonstrate the problem, I can take two identical copies of the | Legacy database (I used the Windows copy and paste to create a copy of | the original file, outside Legacy). Open one, import the other. Let | intellishare do its thing. With my test case, I get 89 individuals | flagged as having changes made to the Notes fields. Same number of | differences with V6 and V5-latest. | | My test case is here: | | http://www.albemarle-callaway.com/problem-report/ | | file name original-herring.fdb. The other files in that folder are | snapshots taken mid-merge of live data. (To show it doesn't only fail | with identical copies; a normal merge with differences has those real | differences interspersed with the spurious ones. It's the fakes which | induced me erroneously handle the merge, thus trashing the integrity of | my hard-won data.) | | I've been using Intellishare merge for months; my procedure hasn't | changed. This problem manifested itself immediately after upgrading to | the new database format. | | Best Regards, | | Ed Barnard in Minnesota, wishing he could be a Legacy user | | 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
