Bill,
"UniVerse/SQL" <-- there's your issue. SQL is enforcing an
INTEGER data type on the SETUP field. You'd have to convert that DICT
item to NUMERIC[1] (I think?) in <8> of an I/D-type or <6> of an
A/S-type. That would define the column as a 1-decimal-place number for
SQL purposes. If it says "INTEGER" there now, that would be
incompatible with a conversion code of MD1.
Did that UV file get converted into an SQL table? Or are you
using an SQL query against that file, where you would normally use a
RetrieVe statement? If "nothing's changed" on your end, it is possible
that UV is now enforcing some SQL constraints that they gave you a pass
on before.
--Ron P
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brutzman, Bill
Sent: Friday, May 06, 2005 9:43 AM
To: '[email protected]'
Subject: RE: [U2] Integer Conversion Codes
The problem happens when I try to run a paragraph with an embedded
UniBasic program that uses a data dictionary with an "MD1" in it.
The error is...
UniVerse/SQL: Conversion "MD1" is incompatible with an INTEGER datatype
<snip>
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
