Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Numerical values as parameters - decimal/separator problem

156019May 4 2006 — edited May 5 2006
I just ran into a small "bug" (don't know for sure if it's a bug, but it looks to me as it could use some kind of fixing), concerning the passing of a numerical value from one page to another, using a link.

I have a report, with one column that acts as a link to a details page. It's a list of orders, and the ordernumber is the link.

In that list of orders, I have a field with "total price", which is a normal number-field, with format mask FML999G999G999G999G990D00
This causes the field to be displayed like this: "$123,456.00" (without the quotes, of course) when there is 123456 in the database.

Now, I want to pass this price on to the details page, because on the details page it can't be edited, it is just displayed. I want to limit the database-action as much as possible, therefor I dont think it would be nessecary to only pass the record-id, and then retrieve the same data again from the database.

The problem is, when the link is generated, the value "$123,456.00" is passed through to the next page. So it is the formatted data, not just the data that's in the table (123456). This will result in that the field on the details page is filled with "$123" because the comma separates the parameters, and ApEx thinks the "456.00" is the next parameter.

Is this a known "problem"? Is there an easy way around this, without using unnessecary database queries?

I can imagine that this can also result in unwanted situations where the decimal character is set to a comma, like the way most European countries have it.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 2 2006
Added on May 4 2006
4 comments
603 views