I'm sure someone will correct me if I am wrong ,
but the output of an ICONV "MD" call is always an integer.
contary to the documentation [uv] the decimal places in the mask is ignored for
ICONV.
the critical item is the scaling factor.
in your example, the iconv would be used to generate internal storage format,
however your oconv is doing simple output formatting unrelated to internal
format.
if you are going to be OCONVing a number that could be either internal or
external ( including a decinal point ) format :
use ICONV "MD11" to convert to internal format
and OCONV "MD11P" to convert both internal or external format to
output formatting.
Gerry
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Lembit Pirn
Sent: Wednesday, April 06, 2005 03:24 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] UDT ICONV/OCONV
Hi !
Can anybody explain, why
ICONV('11.2333','MD10)=11
but OCONV(11.2333,'MD10')=11.2
Is it a bug ?
--
Lembit Pirn
7+7 Software
Tondi 1
Tallinn 11313
tel. +372 6566232
[EMAIL PROTECTED]
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
