I don't see why this would be an issue with Eloquence one way or the other.
Image does absolutely no data type checking.  You can store an ASCII string
in an R4 or E4 item type.  It makes no difference.  The only time this would
be an issue with Query and other such tools that rely on the item type for
interpretations.




Denys

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On Behalf Of
Wayne R. Boyer
Sent: Monday, April 15, 2002 10:23 AM
To: [log in to unmask]
Subject: Re: From Pascal/V to PASCAL/XL

In a message dated 4/15/02 3:18:32 AM Pacific Daylight Time,
[log in to unmask] writes:


> You will want
> to over time, convert the Image DB reals over to native IEEE reals instead
> of the compatability HP reals.

This statement has a lot of potential importance that isn't obvious.  Using
an international standard method of storing real type numeric data is of
course, superior to using an old, phased out proprietary format.  Does
anyone
know yet if HP Eloquence supports the old classic / compatibility real data
type?  If it doesn't, then this could be a BIG issue for any organization
thinking of migrating their applicationt to Eloquence.

Wayne Boyer
Cal-Logic

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *