On Fri, 20 Jan 2006 20:00:35 -0700, "Geoff Rasmussen" <[EMAIL PROTECTED]> wrote:
>>From http://legacynews.typepad.com/legacy_news/2006/01/legacy_update_n.html: > >Publishing Center Fixes: > >- Compiler and Credit lines were printing above the bottom line for the >"Additional" pages such as Preface, Forward, etc. Fixed. >- Fixed some RTF format issues. When is the problem I reported just before the cruise going to be fixed? Below is a copy of the correspondence Ken and I had. Ken issued a last minute update just before he left on the cruise, but the update did not fix the problem. Dennis -- >To: "Dennis Kowallek" <[EMAIL PROTECTED]> >Subject: Re: Serious problem in V6? >From: "Ken McGinnis" <[EMAIL PROTECTED]> >Date: Fri, 14 Oct 2005 12:21:22 -0700 > >Thanks for helping figure this one out. I have it fixed and we'll do a build >right away. > >Thanks > >Ken McGinnis >Millennia Corporation >[EMAIL PROTECTED] >http://www.LegacyFamilyTree.com >We are changing the world of genealogy! > >----- Original Message ----- >From: "Dennis Kowallek" <[EMAIL PROTECTED]> >To: "Ken McGinnis" <[EMAIL PROTECTED]> >Sent: Friday, October 14, 2005 10:14 AM >Subject: Re: Serious problem in V6? > > >I have duplicated the Bug (with a capital 'B'). I'd really like to hear the >explanation for this one! > >If I go into the Publishing Center and preview my book, every individual I >edit from that point on comes up with the short location names in birth, >baptism, death, and burial place instead of long location names. So if I hit >Save on that window, 4 new locations get added to tblLR. > >I'm glad I'm not going nuts. > >When will we get a fix for this? > >-- > >Dennis > >*** > >On Thu, 13 Oct 2005 23:05:22 -0700, "Ken McGinnis" ><[EMAIL PROTECTED]> wrote: > >>Hi Dennis, >> >>I cannot reproduce this problem. Can you open up the Sample file and play >>around with it and see if you can figure out how to make the Short locations >>show on the Edit screen. I think that once they show on the edit screen that >>they had to be messed up somewhere else first. Can you remember what you >>were >>doing that might have caused this? >> >>Thanks >> >>Ken McGinnis >>Millennia Corporation >>[EMAIL PROTECTED] >>http://www.LegacyFamilyTree.com >>We are changing the world of genealogy! >> >>----- Original Message ----- >>From: "Dave Berdan" <[EMAIL PROTECTED]> >>To: "zKen McGinnis" <[EMAIL PROTECTED]> >>Sent: Thursday, October 13, 2005 10:53 AM >>Subject: Fw: Serious problem in V6? >> >> >>> This is in your arena... >>> >>> Thanks, >>> -- >>> Dave Berdan >>> Millennia >>> [EMAIL PROTECTED] >>> www.LegacyFamilyTree.com >>> >>> >>> ----- Original Message ----- >>> From: "Dennis Kowallek" <[EMAIL PROTECTED]> >>> To: <[EMAIL PROTECTED]> >>> Cc: <[EMAIL PROTECTED]> >>> Sent: Thursday, October 13, 2005 6:44 AM >>> Subject: Serious problem in V6? >>> >>> >>> Dave: >>> >>> I am writing you directly about this potential problem in V6 because I think >>> it needs prompt attention. >>> >>> This is difficult to describe, so please bear with me. >>> >>> I have my options set up to display short location names on screen views. >>> Today I opened a database to the family view in V6. Those short location >>> names >>> were being displayed as expected. Then, when I opened up an individual's >>> information screen, I just happened to notice that the short location names >>> were being displayed there also. At first I thought this was odd, but >>> possibly >>> this was a new feature in V6. But this didn't make any sense. >>> >>> So I opened up tblLR in Access and found what appear to be 5 new rows at the >>> very bottom of the table that I am positive I did not knowingly add. >>> >>> Here is one of the correct tblLR rows... >>> >>>>614 Topolyán, Zemplén, Hungary 1 Hungary, Zemplén, Topolyán 0 Topolyán 0 0 >>> 0 0 >>> >>> Here is one of the new rows that somehow has gotten inserted (and is now >>> being >>> pointed to by this individual)... >>> >>>>897 Topolyán 0 , , Topolyán 0 Topolyán 0 0 0 0 >>> >>> As you can see, this new row consists of what was the short name from the >>> original row in both the short and long name of the new row. >>> >>> Looking at backups from the past few days, it appears that the anomaly >>> happened yesterday (10/12). I have a backup from 10/11 which does not >>> exhibit >>> the problem. The backup from 10/12 does. From what I can tell, only the >>> locations associated with two individuals (that I happened to update >>> yesterday) are a problem. Not every individual I updated since yesterday is >>> affected. >>> >>> But I did find one problem in another database I updated yesterday also. >>> >>> The backups are at... >>> >>> http://www.iglou.com/members/kowallek/zajacz-20051011.zip >>> http://www.iglou.com/members/kowallek/zajacz-20051012.zip >>> >>> ...if you want to have a look. Compare RINs 217 and 218. >>> >>> I am running 6.0.0.66. I installed V6 on 10/11. >>> >>> Please get back to me as soon as possible. I am not going to be updating my >>> database until I hear back from you. >>> >>> -- >>> >>> Dennis M. Kowallek >>> [EMAIL PROTECTED] >>> >>> ****************** -- Dennis M. Kowallek [EMAIL PROTECTED] ****************** Legacy User Group 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
