> It sounds good and would really be great if it is backward > compatible. That could solve a lot of problems moving Legacy > around to be updated on different computers and/or around the > country.
That doesn't follow. As has been pointed out, this can still be killed if Legacy writes to the registry or installs anything in the system directory. The MS .Net programming model is getting away from the use of the registry (which many programmers feel was a poor idea in the first place), but I don't know what Legacy does on that. I haven't made a particular study, but from what I've been told by people at Legacy it could also be that Legacy is dependant on specific database drivers that are part of the OS, and this could be a problem in moving between machines. Maybe somebody from the company could answer this. Glen 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
