I use queries in MS Access to preprocess (ie, move data around) the Legacy “fdb” database (in a temporary fdb file) so that Legacy can create a gedcom (using the “Legacy” option) that best displays my data in TNG.
The main issue I have with the transfer of data from Legacy to TNG is with sources and media. I am an extreme “splitter” – meaning that every source document is given a Master Source name. I name and file my sources, and associated media files, using the File ID (3225 in the example below). My source names typically look like this: Source List Name: 3225 - City Directory, CA, Santa Rosa; 1918 - Adelbert G. Quigley Family To achieve a “true” alphabetical sort of the sources in TNG, I use MS Access queries on tblBR (Media Files) and tblSR (Sources) to change the Master Source name to: Source List Name: City Directory, CA, Santa Rosa; 1918 - Adelbert G. Quigley Family [3225] I leave the File ID in the name so that I can search for it in TNG, which allows ad hoc searches. My media files typically look like this: Picture File Name: 3225_IMG.jpg Caption: City Directory, CA, Santa Rosa - Adelbert G. Quigley Family; Date: 1918 I use MS Access queries on tblBR (Media Files), tblSR (Sources) and tblAR (Addresses, incl. Repositories) to change the media file data so that it shows the date and adds the repository for display in TNG: Picture File Name: 3225_IMG.jpg Caption: City Directory, CA, Santa Rosa - Adelbert G. Quigley Family; Description: 1918 [from Ancestry.com] The queries also allow me to check for missing or incorrect File IDs for sources and media, and for missing Repositories. These omissions/errors have to be corrected in Legacy before the query process is completed. >>>>>>>>>> Regarding Scott Hall’s original question about transferring User ID values to the Find a Grave ID, it looks like this could be relatively easily done with queries in MS Access. The User ID is in the UserRef field in tblIR (Individual List). The FAG ID is in the Value field in tblIV (Find a Grave List). The two tables are linked by the common ID field. Obviously, you should work with a copy of your fdb file until you confirm that your queries work. Another option would be to export fields from each table and work with them in MS Excel and then copy back into MS Access. Donald Quigley Escondido, CA <https://donquigley.net/> Quigley Doyle Family Tree From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Rick Koelz Sent: Thursday, July 13, 2017 7:44 AM To: Legacy User Group <legacyusergroup@legacyusers.com> Subject: Re: [LegacyUG] New features suggestion Yes, Donald, Tell us more about what you're doing with MS Access. On Wed, Jul 12, 2017 at 11:53 PM, Chris Bayley <krispi...@gmail.com <mailto:krispi...@gmail.com> > wrote: Donald, Could you please elaborate further on your "preprocessing" in MS Access. I was also a keen user of Ltools with its ability to have more focused queries. Thanks, Chris. On 13/07/2017 4:54 a.m., Donald Quigley wrote: Scott, Without getting into the FAG question, which others have commented on, I’ll second your suggestion that Legacy would be much improved by adding simple database tools (like the old LTools) to accommodate changes brought about by program updates or other user-specific reasons to move data around and do “global” manipulations electronically rather than manually. I now use MS Access to “preprocess” my Legacy fdb database before creating a GED file for uploading to my family (TNG) website and to Ancestry. A Millenia-built set of tools to do similar and other functions would make my life a lot easier by not having to write Access queries as I need them. Donald Quigley Escondido, CA <https://donquigley.net/> Quigley Doyle Family Tree From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Scott Hall Sent: Tuesday, July 11, 2017 2:58 PM To: LegacyUserGroup@legacyusers.com <mailto:LegacyUserGroup@legacyusers.com> Subject: [LegacyUG] New features suggestion I submitted this through Milennia's suggest feature on their website, but also thought I'd post it here. It's great that Milennia keeps adding feature to LFT, but it would be really useful if you also added a way to convert existing data to take advantage of new features. For example, Find-a-Grave has been added to the SourceWriter, but no way has been provided to convert/update existing data using a different source template to the new one. This leaves the users either having to keep two sources for the same source, or manually identify and update the records -- for users with large files, that's a pain. In my case, given that LFT had no dedicated place to record Find-a-Grave memorial I use the flexible field "UserID" BUT ... when v9 added a dedicated field, there was no easy way to convert all the data in the flex field to the new field. In other words, we need some simple database tools added to the program. Perhaps not as much as the old LTools provided, but enough to be able to have a clean, consistent database that takes advantage of new features. For reference, my database is 102,100 individuals and growing. Manually moving data around is onerous. Thanks, Scott -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com <mailto:LegacyUserGroup@legacyusers.com> To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
-- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
