Calculated field and or Variable

[preston2]

On my invoice form I have a calculated field that adds up the total quantity of items ordered in a browse on the form. I do not have any trouble getting the correct value into the calculated field using

total(Invoice_Items->Quantity,GRP->INVOICE_HEADER)

. It also works with this:

total(Invoice_Items->Quantity,GRP->INVOICE_HEADER,GRP->Invoice_items)

The problem is I cannot find anyway to use the contents of a calculated field in another action or xbasic script to preform additional calculations.

I have also tried specifying a variable with something like this.

DIM SHARED V-Items AS n
V-Items = parentform:Items.value

While I have had limited success trying to use a variable, when I do get it to work inside some script the value the variable pulls in is always from the first record in the table and not the current one.

I will have a button on the form that when pushed it needs to get the total of the items and have that value available for use in the rest of the calculations that will be run when that button is pushed.

inv1.png

[preston2]

Re: Calculated field and or Variable

I believe I was able to solve my problem by going at it differently.

I was able to get the correct values written to a field using this code. Now hopefully I can use the value written to that table field in additional calculations.

'Set 'Value' property of 'Order_quantity' in Form 'invoice' .
DIM form_name as c
if is_object(topparent.this) then 
	form_name = topparent.name()+".this"
else
	form_name = ""
end if 

DELETE expression_result
expression_result =  eval("total(Invoice_Items->Quantity,GRP->INVOICE_HEADER)",form_name)
parentform:Order_quantity.value = expression_result

[SNusa]

Re: Calculated field and or Variable

Calculated fields are designed to be used in browses, and also for totals. (total fields on forms/reports, and calculated fields when the database doesn't contain the value s you wish to display)

For what you're trying to do, you may not want calculated fields, you probably want to use variables. And to get totals, I think you'll need to learn some X-basic functions. ~Or, you could place a hidden calculated field on the form, and grab the value from the field. (And possibly place the value into a variable.)

example: vc_TextValue = Form:FieldName.value or optionally try this: vc_TextValue=Form:FieldName.text

The first one example will work here, not the second one. The reason I added the second one is that sometimes, when you can't get what you want using the .value property, the .text property works. I've had to convert action scripts to X-basic just to change this to make them behave properly in some strange situations.....

Note: The expression builder also can show you how to format the code that will work in X-basic. (as Keith indicates below)
He is also much more seasoned than I presently am with a5. (Regardless, I always try to do things with X-basic without resorting to using the -> (pointer stuff) though. It works nicely in the a5 GUI, but IMHO, it seems weird to place that stuff in "real" code.)

"The pointer stuff" used to really throw me off until I began thinking of it this way:

this CALC field literally points (->) to a VALUE
this FORM field literally points (->) to RECORDFIELD etc....

[Keith Hubert]

Re: Calculated field and or Variable

Hi Preston,

First thing, I notice on your screen shot that you have just the one field for the number of colours. To me that means all garments on this Order/Invoice will have 1 colour. Will you have to make out a new record if the customer wants a garment with extra colours?

To use a calculated field within another calculated field, first create it in the Expression Builder, (click on icon shown in red box). Have a look at the attached screen shot and then open AlphaSports to see how it was done.

PS. Hows your Matrix doing?

[preston2]

Re: Calculated field and or Variable

Calculated fields are designed to be used in browses, and also for totals. (total fields on forms/reports, and calculated fields when the database doesn't contain the value s you wish to display)

For what you're trying to do, you don't want calculated fields, you want to use variables. And to get totals, I think you'll need to learn some X-basic functions.
Or, you could place a hidden calculated field on the form, and grab the value from the field. (And possibly place the value into a variable.)

example: vc_TextValue = Form:FieldName.value or optionally try this: vc_TextValue=Form:FieldName.text

I tried using a variable and even placing the value of a calculated field into a variable but it does not work for me with my limited knowledge of X-Basic. I am still learning but I was able to get a suitable (for now) solution as stated above in message #2

[preston2]

Re: Calculated field and or Variable

Hi Preston,

First thing, I notice on your screen shot that you have just the one field for the number of colours. To me that means all garments on this Order/Invoice will have 1 colour. Will you have to make out a new record if the customer wants a garment with extra colours?

To use a calculated field within another calculated field, first create it in the Expression Builder. Have a look at the attached screen shot and then open AlphaSports to see how it was done.

Hi Keith,

You are correct that the form in its current state only has one field for the number of colors in one location but that is because I am still testing. Once I get it to work for one print location I will then tackle adding the other 3 possible locations.

Baby steps for me right now Keith.

I have scaled the thing down to only cover up to 8 colors per location. That will satisfy a large majority of small shops. After that I will get with you or Tom about streamline up things for more color options like we discussed in the private messaging.

[Keith Hubert]

Re: Calculated field and or Variable

Hi Preston,

For the number of Locations, (the same for colours) all you need to do is have each field in the browse with a simple dropdown for choices.

Do you understand now how the calculated fields work?

[preston2]

Re: Calculated field and or Variable

Hi Preston,

For the number of colours all you need to do is have the field in the browse with a simple dropdown for choices.

Do you understand now how the calculated fields work?

I understand how to create calculated fields on a form but they seem to be of little use other than displaying the results on the form.

For the color count I set up the drop down like this.
color-count.png

[SNusa]

Re: Calculated field and or Variable

I tried using a variable and even placing the value of a calculated field into a variable but it does not work for me with my limited knowledge of X-Basic. I am still learning but I was able to get a suitable (for now) solution as stated above in message #2

Here's the "magic (total function) that worked for you":
(Also, I believe the eval function "evaluates the funky calculated field pointer stuff" so that it works in X-basic. It also can convert character values to numbers) ie: x=eval("00010") returns the value of x=10

eval("total(Invoice_Items->Quantity,GRP->INVOICE_HEADER)",form_name)
parentform:Order_quantity.value = expression_result

or "simplified"
parentform:Order_quantity.value = eval("total(Invoice_Items->Quantity,GRP->INVOICE_HEADER)",form_name)

"Baby steps...." ~ I hear ya! Good luck!

[Ray in Capetown]

Re: Calculated field and or Variable

Preston -
variable name V-Items will not work reliably
Start there.
If still no luck then post a sample otherwise we haveto guess if you are using correct object names.

[preston2]

Re: Calculated field and or Variable

Preston -
variable name V-Items will not work reliably
Start there.
If still no luck then post a sample otherwise we haveto guess if you are using correct object names.

I tried it with different names like "Items2" and it still did not work.

[SNusa]

Re: Calculated field and or Variable

I tried it with different names like "Items2" and it still did not work.

He means use variables that make sense to others who are trying to figure out what you are trying to accomplish. Like vc_FName, vc_LName, vn_ItemAmt, vd_StartDate etc.... v for variable, c for type character, n for type number, d for type date etc.....

If you construct readable code, and follow some standards..... Others will be able to better understand what your intentions are.

[preston2]

Re: Calculated field and or Variable

He means use variables that make sense to others who are trying to figure out what you are trying to accomplish. Like vc_FName, vc_LName, vn_ItemAmt, vd_StartDate etc.... v for variable, c for type character, n for type number, d for type date etc.....

If you construct readable code, and follow some standards..... Others will be able to better understand what your intentions are.

Oh. Ok I will try to figure that out.

So for the variable thing I posted above in message #1 I posted it like this.

DIM SHARED V-Items AS n
V-Items = parentform:Items.value

So you are saying I should have stated it here as vn_V-Items ? I thought the "V-Items AS N" made it clear it was a number variable. Am I still missing something?

[Keith Hubert]

Re: Calculated field and or Variable

Hi Preston,

I understand how to create calculated fields on a form but they seem to be of little use other than displaying the results on the form.

You are correct, that is where they are designed to be used and that is where they would stay. You did not state in your opening thread you wanted to use the values on other layouts.

Why cant you keep the value in a table (field)?

[Allen Klimeck]

Re: Calculated field and or Variable

You should not be using a "-" in your variable name. Alpha will think that you wish to subtract a variable "Items" from a variable "V"

Allen

Declaring a Variable