Setting variables onfetch

[rlgiordano]

On my main form which is based on a set, I am trying to set variables ( name, address, etc..) from the parent table.
But when I navigate through the records the variables don't change.
I have them set on the onfetch event . vname =cif->name etc..
What am I doing wrong?

Thanks
BobG

[Stan Mathews]

Re: Setting variables onfetch

No sample attached so we have to play 20 questions.

What is the scope of the variables? Where did you define them?

[rlgiordano]

Re: Setting variables onfetch

Set variables on main menu as global.

[johnkoh]

Re: Setting variables onfetch

Bob,

Call as local variable and write <object, your_variable_name>.refresh()

[Stan Mathews]

Re: Setting variables onfetch

Your code

vname =cif->name

doesn't refer to a global variable. It refers to a local variable, in the absence of other instructions.


Dim global vname as C
vname =cif->name

This tells Alpha that you want to do something with the global variable vname and are not working with a local variable.

Note: Dim global vname as C doesn't change the value of a previously established variable. It only tells Alpha that for the purposes of the current code you mean to do something with the global variable.

[rlgiordano]

Re: Setting variables onfetch

So is everyone telling me that the GUI interface of alpha is not reliable, and that I should use code.
Example, My Main Menu, I go to Form > Variables> Global Tab and than define variable by genie , ie vname="".
Next I select the form from the menu and set that variable onfetch with the value from the table vname= cif->name.
This work for the first record, but when I goto the next record it doesn't change.

[Stan Mathews]

Re: Setting variables onfetch

Nobody said the GUI is unreliable. For someone who's done it several times in the action scripting mode and seen the code behind it the code is familiar.

If you use action scripting you can see that you have to choose the scope of the variable there as well.

var.png

Below is the xbasic behind the action script in the screenshot.

'Get 'Value' property of 'Name' in Form 'Untitled' .
DIM GLOBAL cvariable AS c
cvariable = parentform:Name.value

If the variable is a session/shared variable, first tab of the variable definition genie, and you create an action script to set it to a field value the xbasic behind it is

'Get 'Value' property of 'Name' in Form 'aaa' .
DIM SHARED cvariable AS c
cvariable = parentform:Name.value

In neither case can you omit the dim statement without Alpha thinking you are simply creating a new local variable.

[rlgiordano]

Re: Setting variables onfetch

Hi Stan,
I not talking about the action script, but the tool bar in design mode for forms.
Forms >variables> global tab. define variables.
Why doesn't that work?

Bob

[Stan Mathews]

Re: Setting variables onfetch

I don't think it matters where you define the variable. The issue is that your code doesn't tell Alpha to specifically refer to the global variable. Without a dim statement in the code Alpha assumes you are creating a new local variable and assigning a value to it. The global variable placed on the form is a different thing.

[rlgiordano]

Re: Setting variables onfetch

Stan I get what you are saying.
If you can be patient with me, I would appreciate it.
OK I have a quote number which has to be passed to Reports. Say vQuote.
I declared it on my main menu form Using from the tool bar forms> varaibles > global: vQuote="".
This is where I get confused. When I go to the quote form and get the quote number into the variable vQuote, where and how would I do that.

Thanks Bob

[Tom Cone Jr]

Re: Setting variables onfetch

Bob its easier to help you if you supply sample data and forms.

If the object in your form that contains the quote number from your table is named "QuoteObject", and
If the quote number is character data; and
if the quote number is in the parent table of the set supporting your form...

then you can update the variable value in the form's onFetch event with a script like this:

' onFetch event in form
dim global vQuote as C
vQuote = this:QuoteObject.value

Use the drag/drop list to put the variable on your form and watch it change as you fetch through your records.


if your script says this:

vQuote = this:QuoteObject.value

the quote number gets stored in a local variable named vQuote. Why? Because in xbasic, all variables are assumed to be local to the script unless you specify a different scope with a dim statement.

Yes, its easily possible to have multiple variables all name vQuote...

[Tom Cone Jr]

Re: Setting variables onfetch

Bob said:

So is everyone telling me that the GUI interface of alpha is not reliable, and that I should use code.
Example, My Main Menu, I go to Form > Variables> Global Tab and than define variable by genie , ie vname="".
Next I select the form from the menu and set that variable onfetch with the value from the table vname= cif->name.
This work for the first record, but when I goto the next record it doesn't change.

You were probably updating a local variable with the same name, instead of the global variable, for the reasons outlined in my previous post. The GUI in Alpha Five is reliable.

[rlgiordano]

Re: Setting variables onfetch

Hi Tom,
So on the onfetch event in form, I create an inline xbasic action script to put
dim global vQuote as C
vQuote = this:QuoteObject.value

[Ray in Capetown]

Re: Setting variables onfetch

Bob, think of it like this

1. You need to give the variable a value every time a record is fetched.
2. You need to design a form that displays this variable as an object

1. Is done with on fetch, 2. is not.
1. can be done without 2. if you want the variable present only for coding or calc purposes
2. Allows you when designing a layout to place the object. It does not re-assign any value but by default.

BOTH are required for what you are describing. You then have two placeholders for the table value. One a variable and 2 a form object.
You can choose in your process to use either. Although addressed differently they will return the same value.

SCOPE (shared for example) together with the identifying NAME links the two so that the correct value from table is assigned to the same variable that is displayed

[Tom Cone Jr]

Re: Setting variables onfetch

Bob,

Yes, that should work just fine.

If your form is based on a set of tables you may find that the second line should use the actual form name, instead of the relative object name "this".

Can't test this here cause you've supplied nothing for us to work with.

Let us know how it goes.