Re: [LegacyUG] Ibid. in reports

2012-03-11 Thread Robert Runion
s me crazy. It's one more > little quirk of Legacy that's easy to forget when making source entries > according to Evidence Explained. I also don't think omitting it solves the > "ibid" problem. Marianne > > -Original Message- >> From: Robert R

Re: [LegacyUG] Ibid. in reports

2012-03-11 Thread mbstx
. I also don't think omitting it solves the "ibid" problem. Marianne -Original Message- >From: Robert Runion >Sent: Mar 11, 2012 9:47 AM >To: LegacyUserGroup@LegacyUsers.com >Subject: Re: [LegacyUG] Ibid. in reports > >I think I misspoke in my ear

Re: [LegacyUG] Ibid. in reports

2012-03-11 Thread Jenny M Benson
On 11/03/2012 15:46, Ron Ferguson wrote: > Do you think that it might be there for extreme splitters:-)? !! Even so, I don't think they'd need to use both, just one or the other. -- Jenny M Benson Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages af

Re: [LegacyUG] Ibid. in reports

2012-03-11 Thread Ron Ferguson
Jenny, Do you think that it might be there for extreme splitters :-)? Ron Ferguson http://www.fergys.co.uk/ -Original Message- From: Jenny M Benson Sent: Sunday, March 11, 2012 3:28 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Ibid. in reports On 11/03/2012 14:47

Re: [LegacyUG] Ibid. in reports

2012-03-11 Thread Jenny M Benson
On 11/03/2012 14:47, Robert Runion wrote: > Also, I'm still trying to fathom the significance of a 'File ID' when > applied to a Master Source and a 'File ID' as it may relate to a > Detail entry. I don't think I have ever seen a need to use both the Master File ID and the Detail ID. As a rule, m

Re: [LegacyUG] Ibid. in reports

2012-03-11 Thread Ron Ferguson
am open to contradiction, as I have not checked this for years since I now have so few. Ron Ferguson http://www.fergys.co.uk/ -Original Message- From: ArdenholmeGenealogy Sent: Saturday, March 10, 2012 10:00 AM To: LegacyUserGroup@LegacyUsers.com Subject: RE: [LegacyUG] Ibid. in reports Thanks M

Re: [LegacyUG] Ibid. in reports

2012-03-11 Thread Robert Runion
age (Baltimore, MD: Gateway > Press, Inc., 1978), 237. > > > Subsequent citations: > > Slade, Lamar County Heritage, 237. > Slade, Lamar County Heritage, 142. > Slade, Lamar County Heritage, 68. > > Even though the page number changes,,you should still be using the s

RE: [LegacyUG] Ibid. in reports

2012-03-11 Thread Michele Lewis
still be using the short citation. Michele -Original Message- From: Kirsten Bowman [mailto:vik...@rvi.net] Sent: Sunday, March 11, 2012 1:35 AM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Ibid. in reports Jemima, Marianne, and Bob: Identical source citations should not

Re: [LegacyUG] Ibid. in reports

2012-03-10 Thread Kirsten Bowman
Jemima, Marianne, and Bob: Identical source citations should not repeat in reports. There are certain conditions that will cause them to do that but these can be corrected. To get help from the LUG list you need to identify the specific report you're generating, whether the repetition is in foot

Re: [LegacyUG] Ibid. in reports

2012-03-10 Thread Robert Runion
ge- > From: mbstx [mailto:msz...@mindspring.com] > Sent: 09 March 2012 18:47 > To: LegacyUserGroup@LegacyUsers.com > Subject: Re: [LegacyUG] Ibid. in reports > > I don't think it's available, and I think it should be. I've had a horrible > time creating reports th

RE: [LegacyUG] Ibid. in reports

2012-03-10 Thread ArdenholmeGenealogy
Thanks Marianne I think I will report a suggestion. Jemima -Original Message- From: mbstx [mailto:msz...@mindspring.com] Sent: 09 March 2012 18:47 To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Ibid. in reports I don't think it's available, and I think it should

Re: [LegacyUG] Ibid. in reports

2012-03-09 Thread mbstx
I don't think it's available, and I think it should be. I've had a horrible time creating reports that require the use of "ibid", and no longer use Legacy to do so, I use just Word, which creates a LOT of extra work. Marianne -Original Message- >From: ArdenholmeGenealogy >Sent: Mar 9,