After looking at your example, I agree that it could well be a problem with 
double spaces.
Explanation:
Words and characters wrap differently with different fonts, views, etc.
What’s at the end of one line in one view or font could be in the middle of a 
following line in another view or font.
Hence,
It you have double spaces at the end of a row in one view or font it would not 
be apparent, but in another view or font that might shift to the middle of a 
word … leaving a strange space in the middle of a word.



On 14 December 2013 15:04, Jay 1FamilyTree <1familytree....@gmail.com> wrote:

My problem is not double spaces, but broken words





Here is an example with the broken words in bold



Myra H. Thielen, age 92, of 1619 Armstrong St., Marinette, passed aw ay on 
Saturday, June 3, 2006, after a short battle with cancer. She was bo rn on 
November 29, 1913 to the late  Benjamin A. and Sophia (Bauknecht) Ha nsen in 
Manitowoc. She graduated from Manitowoc High School and from the M anitowoc 
County Teacher College. She married Lester F. Thielen on  Februa ry 9, 1937 in 
Manitowoc. He preceded her in death on May 30, 2000.

She was an active member of St. James Lutheran Church and served as Financ ial 
Secretary for 10 years, and was a member of the Lydia Circle and the c hurch 
choir She was also a  member of the Marinette County Historical Soc iety, the 
Marinette Mental Health Assoc., a Past President of the Marinet te Woman's Club 
and Easter Seal Society, and a charter  member of the Chap ter BK P.E.O. 
Sisterhood and a member of the Sons of Norway. She was a mem ber of the walking 
club and many bridge clubs.

Myra is survived by six children: Mark (Ruth) Thielen, Peter (Mary) Thiel en 
both of Marinette; Paul (Mary Ann) Thielen of Greendale, WI; Jean (Will iam) 
Everson of Fond du Lac;  Anne Thielen of Hortonville, WI and Karn (Pa ul) 
Gregoire of Rhodes, IA; two brothers, Ben (Florence) Hansen of Everet t, WA and 
Philip (Sue) Hansen of Merritt Island, FL; many  grandchildren a nd 
great-grandchildren, who loved her dearly.

In addition to her husband, Lester, three brothers, and a sister preced ed her 
in death.

Friends may call at the Thielen Funeral Home 1403 Newberry Ave. Marinet te on 
Tuesday, June 6 from 4-7 p.m. Funeral Services will be held on Wedne sday, June 
7 at 11a.m. at St  James Lutheran Church with Pastor Darrel Die rs officiating. 
Burial will be in Forest Home Cemetery







It wouldn't be a problem if it were a couple of hundred, but in reality its 
probably well over 20,000



But thanks for taking the time to help.





Jay















On Fri, Dec 13, 2013 at 6:21 PM, Kathy Thompson <kmthoms...@gmail.com> wrote:

Try a "Search Replace" from the Search menu

Find where > General Notes

Find what > (press the space bar twice to indicate a double space)

Replacement text > (press the space bar once for a single space)



How to find

Tick "Find whole word only"

Tick "Anywhere in the field"

How to replace

Tick "Replace only found text with replacement text"

At bottom of pop-up tick

Come back to this screen after the Search and Replace

Repeat process until no more Double spaces remain





On 13 December 2013 15:27, Jay 1FamilyTree <1familytree....@gmail.com> wrote:

<snipped>



Since the recent mention of the 'spacation' errors, I thought, lets at least 
ask to see if maybe some thing had passed me by in the way of a solution.



I have a large database with over 215,000 persons

At least  18,000  have general notes

and there are over 150,000   event records with notes as well.



So, it's a huge job to some day spell check all of those records....



The built in spell checker almost works, if it only had a variable to check if 
a space were removed would that solve the error.



I'll look around some other places and maybe there is a solution out there some 
where for me.



<snipped>



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





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

Reply via email to