On Sat, 07 May 2005 20:48:45 -0400, Dennis Kowallek <[EMAIL PROTECTED]> wrote:
>The odd thing is that this particular location came from a different Legacy >database I had open a few minutes earlier. It must be a variable or something >that isn't being cleared/refreshed properly. > >I am also using the latest build. Upon further review, I can consistently reproduce the bug by using the [~toPlace] substitution in the event sentence for the event type being requested on the report. Change it to [toPlace] and the problem disappears. P.S. The report may also show NO location at all when there should be one ... again using the [~toPlace] substitution. -- Dennis M. Kowallek [EMAIL PROTECTED] ****************** 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
