Joan, I took a look at the app tonight and I didn't make the mistake I thought I had made. (File this under: I thought I was wrong, but I was mistaken.)
Are you running the MS Access version or the runtime version of the Location Tamer app? If you are running the MS Access version, you may see a warning about possibly unsafe macros or code when you first launch the app. You MUST enable the active content for the app to work. You have my solemn guarantee that I have not written any malicious code in the app. After re-reading the e-mail you sent it looks like you are trying to look at the tables in the database itself before the application has had the opportunity to link the tables. If it is the runtime app you are using, I'll need to scratch my head some more. Terry On Sun, Sep 4, 2011 at 6:28 PM, Terry Foster <[email protected]> wrote: > Joan, > > Could you rename the LincolnTest db to sample,mdb? I think I made a rookie > mistake. I will permanent fix it tonight. > > On Sep 4, 2011 3:28 PM, "Joan Kemp" <[email protected]> wrote: > > Hi Terry, > > > > I've tried this several times, but get stuck trying to 'filter by group' > > > > I get the error message 'C:Documents and Settings\db2admin\my > > documents\Genealogy\locationTamer\sample.fdb' is not a valid path. Make > > sure that the path is spelled correctly and that you are connected to > > the server on which the file resides. > > > > Your file 'Lincolntest' is in the directory C:\LocationTamer, as is my > > file Joan2010.fdb - which is the file I wanted to play with. > > There is no file 'sample.fdb' > > > > I think the problem is that I need a valid file - either > > 'Lincolntest.fdb' or' Joan2010.fdb' as the object for LocationTamer to > > work on - it's looking for 'sample.fdb', which doesn't exist, but how do > > you change the file which LocationTamer is operating on? (eg from > > 'sample.fdb to 'joan2010.fdb') > > > > Sorry I can't get it to work straight off. > > > > Joan > > > > > > > > On 27/08/2011 00:57, Terry Foster wrote: > >> I'm a developer by trade and am fairly adept at Microsoft Access. I > >> love Legacy but I have found all genealogy software sorely lacking in > >> the ability to manage locations and do research on locations in the > >> database. > >> > >> Since Legacy uses MS Access as a back-end I decided to add a form and > >> some code to do what I have always felt all genealogy software should > >> do. I would like someone to vet this work before I submit it to Legacy > >> as a suggested enhancement. Please let me know if you are interested. > >> > >> Here's a few things this form does: > >> > >> Displays all location data. > >> (http://electricfoster.info/SourceDocs/LocationTamer/Screen1.jpg > >> <http://electricfoster.info/SourceDocs/LocationTamer/Screen4.jpg>) > >> Show all events tied to a location > >> (http://electricfoster.info/SourceDocs/LocationTamer/Screen2.jpg > >> <http://electricfoster.info/SourceDocs/LocationTamer/Screen4.jpg>) > >> List all child locations in a parent (All cities in a county) > >> (http://electricfoster.info/SourceDocs/LocationTamer/Screen3.jpg > >> <http://electricfoster.info/SourceDocs/LocationTamer/Screen4.jpg>) > >> Browse to google maps for each location > >> (http://electricfoster.info/SourceDocs/LocationTamer/Screen4.jpg) > >> > >> I have made a user guide, of > >> sorts: > http://electricfoster.info/SourceDocs/LocationTamer/LocationTamer.pdf > >> > >> These features, coupled with the ability to quickly edit and > >> standardize locations in a database, are essential to me. I'm just so > >> happy I can make it work in Legacy. I thought I would share. > >> > >> You will need to know how to import a form and a VBA module into an > >> Access database in order to use this. > >> > >> Please don't attempt this unless you know your way around an Access > >> database and please, always back up your data before trying something > >> like this. I just may not be as good as I think I am! > >> > >> Terry > >> > >> > >> 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 > > > > > 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
