Calculated Field problem - Field Rules

[Fred Daniel]

I have a calculated field in my inventory program that Takes the price of the item and multiplies it by the counted value. When I use the post function to post the new prices to the items it does not calculate the new extended amount as defined in the filed rules (Price time onhand) When I go into the field rules and re-evaluate the field rules for that calculated field it works correctly.
Also if I go down the browse tables and retype the value again it works. There should be a function in Alpha's predefined one that would recalculate all calculated field in a table. Any suggestions? This is posing a real problem for my Inventory App.

[Schulzie]

RE: Calculated Field problem - Field Rules

Is the calc field at table level or form/report level?
efs

[Fred Daniel]

RE: Calculated Field problem - Field Rules

Table leval.

[Selwyn Rabins]

RE: Calculated Field problem - Field Rules


I just added it.

It will be in the next patch.
You can download the new addins now if you prefer not to wait for the next patch.



You can download it at:
http://downloads.alphasoftware.com/patches/system_aex.zip

Exit a5 and unzip this file into your a5 program folder.

When you right click on a table in the control panel, go to utilities. you will see a new command "recalculate calc fields"

If you want to automate this, there is a new xbasic command

for example

t = table.open("customers")
t.Recalc_CalcFields()
t.close()


Thanks.

[Richard Rosen]

RE: Calculated Field problem - Field Rules

Will that command be available in action scripting? Will it impact calculated values on a form?

Thanks

[Tom Cone Jr]

RE: Calculated Field problem - Field Rules

Richard,

My guess is that it would NOT affect calculated display fields on your form. I'm referring to those fields which are defined in your layout, and exist only in memory as variables (and then only while your form is open). They are not fields in your table.

The terminology here is a bit tricky.

Alpha Five field rules permit you to specify that a particular field in your table is to be a 'calculated field' rather than 'user entered' or 'auto increment'.
This defines a table field which behaves in a particular way, and which cannot be modified by the user at run time.

This field rule calc field is very different from the 'calculated field' you are permitted to define in a layout (form or report). I think its helpful to describe these as 'calculated display fields' since they display calculated values on your form or report, but aren't saved in a field in your table.

Often its difficult to know which 'type' of calculated field a person is referencing when they post a message here.

Selwyn's post suggests strongly that the new method will work at the table level, not at the layout or form level.

-- tom

[forskare]

RE: Calculated Field problem - Field Rules

I don't think there's really a need for it to work at the form level since the calcualted fields are automatically updated.

kenn

[Richard Rosen]

RE: Calculated Field problem - Field Rules

Here's my situation. I have a seminar fee field which is updated by an onchange event in another field (early registration). I have a lodging field which is also updated by an onchange event in another field (single, double, triple). I have total cost which is seminar fee + lodging. I have a deposit field which is also updted by changes in single,double,triple. I have additional payment fields of pay2 and pay3. I have balance, which is totalcost - (deposit+pay2+pay3).
Totalcost updates one change behind changes to lodging. When I save record, totalcost is correct but not balance.

Am i doing something wrong?
Thanks.