Hi Laurie,
I really agree with you about the difficulty of version control. I have
complained on this LUG about Legacy changing the file date stamp even if you
just view a database. Seems as though this isn't a Legacy problem but a problem
with the Microsoft database system they use. In my case my database got
corrupted and I needed to compare the Legacy zipped backup files to see which
version one was good. Sometimes when I know I am just browsing I will create a
copy of the data file to use for viewing so the real file doesn't get a new date
stamp.
This is what I do to compare file1 vs file2:
Do this for both file1 and file2.
In Legacy, click File>Export To>GEDCOM File
A window will open-in the top on the Options tab Produce file for: (select)
Legacy, Character Set ANSI
then click Select File Name and START EXPORT
Now you have saved two GEDCOM files which you can compare.
I use WinMerge which is free/open source, user friendly and presents the
differences quite well.
You can get WinMerge here: http://winmerge.org/
When viewing the GEDCOM data note the Update/modified date in the GED file.
This isn't the best solution, i.e. it doesn't do a direct compare of
Sourcewriter sources. And likely some other things I am not aware of.
I spent a lot of time trying to do this. I bought MudCreek GENMatcher hoping it
would do what I wanted but it didn't.
On 1/20/2012 9:32 AM, laurie curtis wrote:
>
> I’m made a mess of things and cannot be the only one with this problem.
> Really lost the plot with version control and have managed to enter new data
> in to back up versions of files. Also because every time a file opens, it gets
> a new date, I don’t always know what file is the newest –just know which
> one I
> opened most recently. This compounds the version control issue when I THINK
> I’m entering data in most current file, but entering it in a back up.
> Because
> I’m afraid to lose what I’ve done, I save the backup with a new name.
> Now I’m
> in a real mess.
>
>
> Would love to know if anyone has figured out a way to compare files for what
> is DIFFERENT. I know we can compare for what is the same, but that won’t
> help
> me figure out which files have new data? Thoughts for how to get myself out
> of this mud hole? Would also really welcome ideas for how people handle file
> management – I obviously need some lessons!!
>
>
> Laurie
>
>
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> 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/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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
