Using Access 2002. As mentioned in other replies, exporting the fdb to a new file appears to have fixed the MS Access problem, but now I'm concerned about the integrity of the original fdb.
Other than the File Management routines, is there any other testing I can perform to 'prove' the original fdb? Thanks. On 6/12/2011 6:59 AM, Brian/Support wrote: > What version of MS Access are you using? You need to have MS Access 2000 > or later. > > Brian > Customer Support > Millennia Corporation > [email protected] > http://www.LegacyFamilyTree.com > > We are changing the world of genealogy! > When replying to this message, please include all previous correspondence. > Thanks. > > On 05/12/2011 3:16 PM, J Richard Nickel wrote: >> Yes, Legacy appears to be working perfectly. > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on > our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
