![]() Each software has more or less its own data model, and there are usually data elements that cannot be mapped cleanly from one data model to the other. it’s almost certain that a certain amount of data will become lost or corrupted. But be aware that almost any conversion of genealogical data from any genealogy software to any other genealogy software can be very fraught. I’ve never been a Legacy user, so I can’t speak specifically to any of your data corruption issues in converting your Legacy 9 data to RM8. So let me try to speak to some of your concerns. I’m also both a genealogist and an IT person (now retired after 50 years in the industry). I’m testing RM8 heavily, but I am many months away adopting it as my production software. I’m a long term and loyal RM user who is relatively happy with RM7 and who is being very cautious about converting to RM8. I think we have given RM8 a good run but it is simply not worth the risk of corrupting data that has been accumulated over a long period of time. If the latter - then again it suggests rushing RM8 to meet a date. Has that function been deprecated or are RM planning to catch up at some point. No announcement of the function being dropped - just simply not present. Already there are reports of defects in 8.0.4 that were not present in the prior 8.0.x releases.įolk have raised a number of issues whereby functionality that existed in RM7 has been dropped from RM8. However, that in itself leads to more defects being introduced. ![]() I guess that the RM folk are totally swamped rushing to fix defects and that may be why they are not responding to problems. If the data after a migration cannot be guaranteed to be 100% accurate then it becomes worthless. Now, I am not a genealogy person, I leave that to my wife - but I am a software R
0 Comments
Leave a Reply. |