In reply to my posting, Sherry wrote:
> There was a problem with the original update we uploaded and had to pull =
> it.
> There's a new update now. Just go to our website, click on Download and =
> select
> Update. Then run that update and all should be well.
>
> The current build is 4.0.0.280 dated 16 Sep 03
Thanks I "maually updated" last night and things appeared to go well,
except that I got an email saying I'd need to use a password, but I didn't
need to use it. The update procedure never asked for it!
And others have reported problems which Sherry isn't able to
duplicate. Perhaps there should be a "new" build with a later date,
say 18 Sep 03? Perhaps Legacy needs to add an update date
in addition to the build date, and then if there is a later update of
the same build the auto-update software will take it, or perhaps
when the dates indicate one has the same date, instead of the
auto-update software refusing to go on, it should ask the user
if (s)he wants to re-install that update?
jr
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
