Spencer,

I see a couple of problems.

1. I'm not sure how predictable it is to check for >"". Use
Not @IsBlank(Company)

2. You don't have any parentheses. Without them, your ors and ands may not be applied as you think. It's hard for me to correct this for you because I don't know what you intend any more than Sesame does.

If (A and B) or C
is not the same as
If A and (B or C)

If you just say:
If A and B or C
...you leave it to the computer to guess what you mean and it may not guess the same way you did.

GRRRR -

I was just in the middle of writing a very lengthy reply - was just about finished - and must have accidently exited from the web-site.  So, without trying to 'justify' WHEN, WHAT, WHY or HOW I came up with that ludicrous programming, (other than to say that in my eagerness to enjoy the results, I probably did it when I was SUPER tired and as soon as I converted my database .. from my memory of Q&A .. knowing that there was a better way that I could always change to later on), here is the bottom line.  

All I wanted is that - when notified that a person was deceased - to have Sesame clear a whole bunch of fields.  (Whether the fields previously contained data or not, therefore, is totally irrelevant).

I have left the "goto" portion of the programming in 'on element exit' and placed my revised programming in 'on element change' since most people only die once.    (By funny coincidence Bob, I had just completed the programming before I saw your reply and, yes, I do believe there IS a logical advantage).  The new code is very simply:

if Status = "Deceased"

then

clear (Company Name, Street Address, Apt, City, State, Zip, EMail Address, Home, CommentsHome, Cell, CommentsCell, Work, CommentsWork, Fax, CommentsFax, Other1, CommentsOther1, Other2, CommentsOther2, Mail Name) 

I trust that, now, what I wanted to accomplish is much clearer (both to Sesame AND Erika).  lol

I thought the previous programming was safe because the IF portion started with the fact that the status had to be deceased AND one of the OR conditions had to exist.  I can see now that because so MANY OR conditions followed the AND, perhaps Sesame couldn't properly interpret it.

Time will tell whether this will rectify my DISAPPEARING DATA issue.  

Thanks folks!

Erika -

You are ABSOLUTELY right - so thanks for 'harping.'  I have already changed the programming replacing GoTo() with ThrowFocus(), and tested it and it works just fine.

Also, because of your earlier reply, I can see clearly that Sesame almost certainly was interpreting my earlier code to (If status = deceased AND Company Name> "") OR ....... and then if ANY of the OR conditions were met .... cleared the fields.

I am confident now that my disappearing data will stay put once I put it back in.

Thank you.  Thank you!!!