Hi, it's me again! This forum has helped me every time in the past and I'm hoping it will help me again.

As I have said before, I am designing a database where any layout in the database can be reached by

choosing two pop-up numerical value lists "Stage" and "Batch". I have created a clever(ish) calculation

that will combine these two values when chosen to return the layout number required, then send

the user to that layout. I am hoping to use this script sent to me. I am having problems with this.

This script starts like this.

Allow User Abort [Off]

Go to Field [stage]

(This is fine. Stop the user from stopping the script and go to the field specified)

Loop

Pause/Resume script ["0:00:01"]

(Start a loop, then pause for a second then carry on)

Exit Loop If [status(CurrentFieldName)<> "stage"]

End Loop

(This is where I have a problem. This checks if that the insertion point is still in the field "stage". You can

spend as long as you like deciding which selection to make. If you've chosen from the pop-up value list

or just clicked out of the field you exit the loop.

My copy of Filemaker doesn't have a <> choice. If I try and key in a "<" followed

by a ">" it stops me. Is "not" what I should use instead? When I have tried to put this script together

the Pause/Resume loop hasn't appeared to stop and my copy of FileMaker locks up. "Exit script" doesn't

appear to stop it. What do I do?)

I intend to perform the calculation and go to the specified layout depending on what was

chosen in one field and remains in the other after this "Pause/Resume" loop, but I can't get any further.

I know this is basic stuff, but I'm putting this together in my spare time for my company and would

REALLY appreciate any help.

<> is a perfectly valid operator and I use it all the time. What it actually means is "Greater Than" and "Less Than", or "Not Equal To". This is mathematically differen than the Boolean "NOT" operator, but either one will work in this situation.

I would recheck your scripting, you must have typed something incorrectly. Also check your version of Filemaker Pro to make sure that it is the latest update. Possibly a bug exists.

Why not simply use the = sign with the / through it (is NOT) ??

In other 'keys' (OPTION and =) *

I even wonder I've ever seen <> as an operator, but I might have overlooked.

Harryk

I prefer the <> character as it is very readable and instantly recognizable for what it is. Or perhaps I just learned to use it back in the days of ASCII only character sets, where we did not have fancy Not Equals characters.

A better expression than Status(CurrentFieldName)<> "stage" in this instance might be...

Exact(Status(CurrentFieldName), "stage") = 0

Remembering that Exact() is case sensitive, I'd use:

Exact(Lower(Status(CurrentFieldName)), "stage") = 0

This will make it more robust and reliable if somebody later decides that they prefer all the field names to begin with capital letters.