I assume you put it in "Global script definitions". I know a couple of us tried that when release 2.5 came out and didn't have any luck.

One option is to create a table for persistent variables. For example, if you had a table named GV and you wanted to access a field named pn you would access it using...

record(GV, 1).pn

You’re welcome Laurent. I don’t mind a work around as long as it isn’t too cumbersome and this one isn’t bad.

Hi, you can define a user function

function pn() do

110

end;

Now you can uses this like let XX := pn() + ...

Günther,

This would be considered a global constant since it is hardcoded, but I really like the possibilities of this approach.

Laurent,

Why ask? Test!!

Here's what I meant about the possibilities...

function myVar(operation : text,num : number) do
switch operation do
case "+=":
record(GV,1).(Number := record(GV,1).Number + num)
case "-=":
record(GV,1).(Number := record(GV,1).Number - num)
case "*=":
record(GV,1).(Number := record(GV,1).Number * num)
case "/=":
record(GV,1).(Number := record(GV,1).Number / num)
end;
record(GV,1).Number
end

This is a combination of both.

Yeah, it looks like filter will not accept any kind of proxy.

You have to take a calculated Field with pn() <compareOperation> .

Then use yes/no in this field to select the valid entries.

It seems like record(GV, 1).pn is best for a single user environment. In a simultaneous multi-user environment, user two could write to the same global variable as user one, causing unexpected results.

What would be a good way to make the the GV table per user, so each user would have their own global variables, based on their email address?

I haven't tried this, but if you add a User field to the GV table and you gave each user their own record in the GV table you could use the select statement to get the value you want. @Westy, it looks like a good modification for your user-defined function.