Legacy uses same database engine that MS Access uses. It is NOT "built" on Access.
The database engine used by Access and Legacy is not slow, at least, not for datafiles of the size and type Legacy users need. I once wrote a genealogy application in Access, simulated a 100K+ data file, and access to records was indistinguishable from instantaneous. Legacy uses 27 tables, and genealogy datasets rarely exceed 25 thousand records. The database engine used by MS Access and Legacy is perfectly suited to such applications. It is true, that the data processing people I know say that MS Acces does not "scale up" very well, particularly on networks. They're talking about databases with millions of records, in hundreds of tables, accessed from hundreds or thousands of terminals. These reports probably account for the "rumbles" that MS Access is slow. Well, my bicycle is slow compared to an airplane, but that doesn't mean I need an airplane to go to the corner store. Since Legacy uses a standard database engine, anyone can write an application to access and manipulate its data. I sometimes use MS Access to view data in tabular format, make search and replace changes, or make queries that are not possible or are very inconvenient within Legacy itself. It is a relatively simple matter to export Legacy tables into MySql data tables. What you do with them after that is, of course, a different matter. 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
