Radicore Forum: Transaction Patterns

Home » RADICORE development » Transaction Patterns » Calculated fields

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Calculated fields [message #4282]

Mon, 23 June 2014 09:20

htManager
Messages: 442
Registered: May 2014

Senior Member

Hi Tony,

can I automatically calculate a field with a method of the radicore framework?

I have three fields, amount_netto, amount_tax and amount_brutto.
I want that the field amount_brutto is calculated automatically after filling out the fields amount_netto and amount_tax.

I used to develop desktop applications in ObjectPAL, a language called Object orientet Paradox Apllication Language for the desktop database Paradox for Windows. In this language I would have put the code in an event of the amount_tax field. But in a web environment with Radicore and PHP I don't know how to do this.

Thanks in advance, best regards,

Juergen

Report message to a moderator

Re: Calculated fields [message #4284 is a reply to message #4282]

Tue, 24 June 2014 04:08

AJM
Messages: 2373
Registered: April 2006
Location: Surrey, UK

Senior Member

No, the framework cannot do such things for you automatically, you have to write the code yourself.

When reading from the database you can build the calculation into the SQL statement such as:

SELECT product_id, unit_price, quantity, SUM(unit_price * quantity) AS extended_price ...

Tony Marston
http://www.tonymarston.net
http://www.radicore.org

Report message to a moderator

Re: Calculated fields [message #4286 is a reply to message #4284]

Tue, 24 June 2014 10:24

htManager
Messages: 442
Registered: May 2014

Senior Member

Isn't there a possibility to change $fieldarray with a custom method (like i.e. _cm_getExtraData) when jumping with the Tabulator from field to field?

Report message to a moderator

Re: Calculated fields [message #4288 is a reply to message #4286]

Tue, 24 June 2014 11:53

AJM
Messages: 2373
Registered: April 2006
Location: Surrey, UK

Senior Member

No. Nothing is sent from the client browser to the application on the server until you press a SUBMIT button. That is how HTML works.

Tony Marston
http://www.tonymarston.net
http://www.radicore.org

Report message to a moderator

Re: Calculated fields [message #4291 is a reply to message #4288]

Wed, 25 June 2014 11:04

htManager
Messages: 442
Registered: May 2014

Senior Member

I changed my database schema by inserting a column with type boolean where you can decide if the field will be calculated or not.

You said that nothing is sent until the submit button is pressed. That's ok for me because I now want to calculate the values after having pressed the submit button.

I tried to put my code for changing the values in $fieldarray in the custom method _cm_preInsertorUpdate($rows) in the class file. I tried to change the values of $rows with $rows['column_name'] = 'foobar'. But I didn't succeed. Is this a possible way or not?

Or do I have to use another custom method?

Report message to a moderator

Re: Calculated fields [message #4292 is a reply to message #4291]

Wed, 25 June 2014 12:08

AJM
Messages: 2373
Registered: April 2006
Location: Surrey, UK

Senior Member

You need to look at http://www.tonymarston.net/php-mysql/functions-and-variables .html#sequence.of.events to see which custom methods are called, and in what sequence, for each transaction pattern. You will notice there that the _cm_pre_insertOrUpdate () method is *NOT* called when the pattern starts with insertRecord ($rowdata).

Tony Marston
http://www.tonymarston.net
http://www.radicore.org

Report message to a moderator

Re: Calculated fields [message #4312 is a reply to message #4292]

Sat, 28 June 2014 09:15

htManager
Messages: 442
Registered: May 2014

Senior Member

Thank you very much. It works perfectly.

Report message to a moderator

Previous Topic:	eMail sent automatically
Next Topic:	Dropdown list

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Jan 08 08:53:22 EST 2025

Total time taken to generate the page: 0.01361 seconds