I had taken the time to rename our accounts without a space.  I thought it would make them more 'key' like.  Of course it was wrong. 

 

There are 3500 records I did this to and now I am hoping that there is a way to quickly undo what I did.  I did it so I could get them with LeftWords.  I searched and looked on the custom functions and nothing now splits it.

 

So take AccrossTheRiverLodge and make it Across The River Lodge.

 

I tried searching for second capital to insert a space before it but I can't even get started on how to look for a capital of any letter.  If no hope, I will spend my day paying my penalty for stupidity.

So take AccrossTheRiverLodge and make it Across The River Lodge.

Instead of "searching for second capital to insert a space before it", you could substitute ALL capitals with a space and itself (i.e. a substitution with 26 value pairs) and apply Trim() to the result.

Well of course that makes perfect sense.  So it would look like this

 

Trim ( Substitute ( SearchKeyField ;

[ "A" ; " A" ] ;

[ "B" ; " B" ] ;

... )

)

 

I tried it with 3 letters and it works so now I just have to finish it.  I wonder how many other things I'll come across that I did wrong when new and (more) clueless (than now). Thank you again Comment.  

Yes, that is correct. A footnote to this: we are assuming no diacritics and/or other alphabet (Greek, Russian) characters were used. Otherwise you would need to go letter by letter. And, of course, with something like "HenryThe8th" you can only guess what the original was.

When I goof I do not mess around but luckily I do not recall any names like that with a number in them.  It was a horrific job when I did it and it became a blur.  I did not know about TrimAll or even Substitute or any functions or scripts and I did it one at a time by hand.  As for other characters I would have deleted them knowing me but I am not positive.  

 

When done I will search for numbers to see if any need manually fixed.  So I would do multiple new record requests on each number up to 9?  Yes of course. You seem to think of all the things I would never think of and I appreciate it very much.

 

I had to look up diacritic.  It was good for me.  I should have known it anyway.  I've only known the term accent.

Enter Find Mode

Set Field [ yourField; "*#*" ]

Perform Find []

Reminder about find operators...

 

So take AccrossTheRiverLodge and make it Across The River Lodge.

 

Hi

 

this is a different approach to the problem.

Split Word.zip

Good to see you again, Daniele.

 

"The12thNight"

Hi Michael

 

I knew that... infact that calculation could be used even to place a space between numbers.

 

Naturally the calculation could be modified to take in account the numbers.

My point is that a machine cannot make a judgement call. You could (with more effort) change the calculation so that it places a space only before the first digit of a group of consecutive digits; but then I will come up with an example where such algorithm doesn't make semantic sense...

 

 

---

P.S. Don't miss:

http://fmforums.com/forum/topic/90657-data-viewer-misrepresents-trailing-returns/?p=416304

Edited January 20, 201412 yr by comment

Hey thanks guys.    I had run the correction immediately and it worked great but I will keep this calculation to learn from, thank you Daniele.  

 

I had searched for numbers first, thank you very much Bruce for the reminder and I fixed them first so all is good.