Global variables using

[dordije]

Hi all.

I am little confused about using global variables.
I declared some of them in Autoexec script, like:

DIM GLOBAL pFIRREC AS N
DIM GLOBAL pFIRNAME AS C

As manuals says we can view all of them in whole application, from the moment database is open up to time we close that database.

1. But, I was in position that when I click on big V in toolbar (when some form is in design mode) I can,t see any of them. I can only define new one.

2. Where can I allways se all of them when designing apllication ?

3. A can,t use them in Default expression in Field rules, etc.

4. Also I can,t use them as arguments in INSERT statement in Active link table (I wanted to place global variable pFIRREC instead argument :new.FIRREC in INSERT statement), but it not succeded.

5. Also, in some thread one expirenced user stated that he defined same global variable for two tables, parent and child table. That also confused me. I thought that once declared global variable is valid and visible in all parts of application and is same for all applicatin objects !?

Can anyone explain what can I expect from global variables ?

Thanks,

Dordije.

[Stan Mathews]

Re: Global variables using

1. But, I was in position that when I click on big V in toolbar (when some form is in design mode) I can,t see any of them. I can only define new one.

The heading for the dialog that appears when you "clck on big V says Define New Variables, not See All Variables.

2. Where can I allways se all of them when designing apllication ?

You should be able to see them in the drag-drop list when designing a form.

3. A can,t use them in Default expression in Field rules, etc.

You should be able to type in the variable's name even if you can't see it.

4. Also I can,t use them as arguments in INSERT statement in Active link table (I wanted to place global variable pFIRREC instead argument :new.FIRREC in INSERT statement), but it not succeded.

No experience with Active link tables.

5. Also, in some thread one expirenced user stated that he defined same global variable for two tables, parent and child table. That also confused me. I thought that once declared global variable is valid and visible in all parts of application and is same for all applicatin objects !?

Not familiar with that thread. Why are you worried about it? You can define a global variable, a session variable, and a local variable with the same name. He/she may have had some reason to ensure that the two tables referenced the golbal entity.

[dordije]

Re: Global variables using

Thanks Stan !

Add 3.
You should be able to type in the variable's name even if you can't see it.

What confuses me in this point is that in simple default expression bulder I can,t in no way see needed global variabe (not with F2,F3 etc), expect that I know its name. In A5 help I can see that I can use F6 Variable, but on my A5 V9 Platinum with update from march I can,t see this F6 ?

But when I pressed F6 I got dialog for geting global variable. Selected global variable is declared as N, but when I click OK I get message "Expression does not evaluate to a Numeric value" ? Both the database field and global variable are numeric !? Why this message ?

Thanks.

Dordije.

[dordije]

Re: Global variables using

Add 3.

I succeded in Default expression for Field rules, using F6, to put expression VAR->pFIRREC, where pFIRREC is global variable.

In expression builder I can see that it is type N and value is 2.
When I click on OK and then click Save I got message "Cannot use function in this context". What is wrong in my expression ?

Thanks,

Dordije.

[MikeC]

Re: Global variables using

Dordije. ,

I got message "Cannot use function in this context". What is wrong in my expression ?

Hard to say (or even imagine!) without knowing what your expression is or the function you have used that cannot be used.

[dordije]

Re: Global variables using

Add 3.

I deleted field rule. Anyway, when testing, in trace window A5 still warns me about errors in evaluating field rule ? I don't have any one !

Also, in A5 help, I can't find correct syntax for FORM.VIEW() method. In help I can't see explanation for sixth parameter, for arguments. Anyway, on the base on threads I use syntax:

FORM.view("frmARTICLES","","","","",mArgs)

My A5 V9 Platinum Version Build is 2095 and System Addin Build is 3264. Does anybody have some newer versions ?

I have downloaded last update. Are they cummulative ? Must I download any previous update in same version, or last update include previous one ?

Are thera are any ghosts on my A5 :)) ?

Thanks,

Dordije.

[dordije]

Re: Global variables using

HI MikeC !

In expression builder I hit F6 and selected global variable pFIRREC. Builder puts VAR->pFIRREC, and say it has value 2 and is Numeric (both are true). Then, I click OK. Nothin happened, seems all is ok. Now I am on Field rules window, tab Data Entry, with next content:

Default mode: Simple default expression
Default value: VAR->pFIRREC

Then I click Save and got message "Cannot use function in this context" !

Dordije.

[MikeC]

Re: Global variables using

Dordije.,
You have to make certain that you have dimmed your variable as global in the autoexec (or wherever you declare it). I was able to reproduce your error message with it not declared global. Make sure you have done this as it works here with the same latest builds as you have.

[dordije]

Re: Global variables using

Hi MikeC,

I surely dimmed variables as global, in Autoexec, as:

DIM GLOBAL pFIRREC AS N

Later, in some of begining forms I initialized it on value 2.
Also, when I in Expresion builder hit F6, and select global type variables, I can see all of them I declared as global in Autoexec script.

Thank you MikeC, I must investigate this further.

Dordije.

[MikeC]

Re: Global variables using

Dordije. ,

As it works here just fine something else is the issue....but, to me, having the Exact same error come up when the variable is NOT dimmed Global and works fine once dimmed global sure is a big coincidence!! But, please report back if the reason behind this surfaces as it is nice to know of other ways in which the same error message will come up if that is the case.

I would approach this from "square one". Make another form with just the minimum. Dim your global variable for this form in the same way as you did for the form's field in question. Set your field rules. If it still happens then submit it here for others to help.

.....without having the same issue as you the only way I could help further would be with a sample that has the same problem.

LATER: I just read a different post that referred back to this one and found

you cannot use a global variable in the default value field rule. (you can for a normal dbf table but not an active link table.

And that it very well could be a bug...Here is a link to the thread. http://msgboard.alphasoftware.com/al...ad.php?t=80085

[dordije]

Re: Global variables using

Hi Mike,

I replied on thread you pointed me to. It appears that it is not possible to use a global variable as the default value in field rule, with Active link tables.

However, I will try to make some simple form and do what you proposed. I will dim global variable for that form and will se what will happen.

Thanks,

Dordije.

[dordije]

Re: Global variables using

Hi Mike,

Meanwhile I made a few new tests with other simple forms. After examining all what happend with global variables and field rules it appears that next is valid (thanks to Tim):

1. When using Active linked tables, we cannot use global variables as default value. For me, main indication is that in Expression builder we do not have listed F6 key (Variables), we can only see F2,F3,F4 and F9. But, no matter we can't see F6 we can press F6 and select global variable, but I thing this is supposed not to be used.

2. We define Field rules on table fields, in Table/Sets tab. I use Active linked tables. When using .DBF tables, I can define that default value for some field is global variable. Interestingly also with .DBF tables I cannot see F6 key in Expression builder, but I can press it. Design of forms do not influence in any way on definng Field rules ant its default values.

Dordije.