Compare 2 fields & delete everything in "field 2" that occurs in "field 1"

Is it possible to compare 2 fields and delete everything in "field 2" that
also occurs in "field 1" ?


FIELD1 800-555-1212 for Waterpocket Fold

FIELD2 800-555-1212 for Red Circle Cliffs

New FIELD2 Red Circle Cliffs

Any suggestions are most welcome

[marianopeterson]

I think you'd have to create a calc field that compares the two fields:

If( field1 = field2, "duplicate", "other")



Then you could search within the calc field for the word "duplicate".
Once you attain your desired found set, then perform a replace on
field2, replacing the contents with "" (emtpy string).


--
Mariano Peterson


Posted via [url]http://dbforums.com[/url]

[Lynn allen]

<aloysius99@sbcglobal.net> wrote:

> Is it possible to compare 2 fields and delete everything in "field 2" that
> also occurs in "field 1" ?
>
>
> FIELD1 800-555-1212 for Waterpocket Fold
>
> FIELD2 800-555-1212 for Red Circle Cliffs
>
> New FIELD2 Red Circle Cliffs
>
> Any suggestions are most welcome

Well, what exactly do you want to delete? Word by word, or longer (or
shorter) strings?

For word by word, it's easy enough. You'll need a global text field and
a global number field counter or two.

Use Set Field to put the first word into a global field (just for
processing purposes, this can be done without this step but it's easier
to see and debug using the holding global), and use Substitute to delete
it from the second field. Then loop through, setting each succeeding
word into the global using Middle Words, using Substitute again, and
incrementing the counters until you run out of words in the first field.
Use the counters to locate yourself within the first field, moving along
from word to word.

Then run a Trim on the second field to get rid of leading or following
spaces. You might also use a Substitute to get rid of more than single
spaces in the middle of the string and cycle through until the field is
clean.

How to handle the last word in the first field is left to the student as
an exercise. ;) And, take note, do NOT turn User Abort (Off) until after
your loop is fully tested and working!
--
Lynn Allen Allen & Allen Semiotics
FSA Associate Filemaker Consulting & Training
[email]lynn@semiotics.com[/email] [url]http://www.semiotics.com[/url]