Arí Ricardo Ody wrote:
First, thaks to everyone that post msgs trying to answer my questions.
I have a weak skill in Lazarus/Pascal if compared with people like you. I can't
understand why you don't solve the trouble instead of try to send the correct
msg error.
As John suggested, I don't
Bram Kuijvenhoven wrote:
Or, Arí has an older odbcconn, where SQL_TIMESTAMP was mapped to
ftTimeStamp, which in turn has no FieldClass associated with it, giving,
on closer inspection, the same error -- 'Unknown field type'!.
In a private mail, Arí told me he has Lazarus 0.9.12. Looking at
Bram Kuijvenhoven schreef:
BTW: is there an easier way to see which FPC revision is shipped with a
Lazarus than just looking at the sources in fpcsrc directory of the
Lazarus distribution?
Not, that I know.
Vincent.
_
To
First, thaks to everyone that post msgs trying to answer my questions.
I have a weak skill in Lazarus/Pascal if compared with people like you. I can't
understand why you don't solve the trouble instead of try to send the correct
msg error.
I would like to give you a suggestion. Here we go:
In
On Sun, 26 Mar 2006, Arí Ricardo Ody wrote:
Why, instead off try to return the wrong error, you don't try to return the value of the
TIMESTAMP as string [26] format. If you're interested I can send you a list
of the DB2 tables and the format that cobol program receive them and a brief
On Fri, 24 Mar 2006, Arí Ricardo Ody wrote:
At 14:40 24/3/2006, Michael Van Canneyt wrote:
(I received a screenshot in private)
Sounds like the error message is formatted wrong:
Unknown field type: HREG_DIVDD
Ricardo, it is not quite clear;
is the field type called HREG_DIVDD or is
Michael Van Canneyt wrote:
Ok, so first of all the error message is somehow wrongly formatted,
instead of giving the ODBC field type, it only contains the field name
(it must do that too, of course), but fails to return the actual
'unrecognized' field type.
Looking in the ODBCConnection, I
Bram Kuijvenhoven wrote:
Michael Van Canneyt wrote:
Looking in the ODBCConnection, I would suppose that the DB2 Timestamp is
translated to SQL_TYPE_UTCDATETIME:
SQL_TYPE_UTCDATETIME:FieldType:=ftUnknown;
SQL_TYPE_UTCTIME: FieldType:=ftUnknown;
I guess that at the moment I wrote
On Sat, 25 Mar 2006, Bram Kuijvenhoven wrote:
Bram Kuijvenhoven wrote:
Michael Van Canneyt wrote:
Looking in the ODBCConnection, I would suppose that the DB2 Timestamp is
translated to SQL_TYPE_UTCDATETIME:
SQL_TYPE_UTCDATETIME:FieldType:=ftUnknown;
SQL_TYPE_UTCTIME:
Bram Kuijvenhoven wrote:
I'll be right back with a version of odbcconn that tries giving a more
meaningful error using the sqlGetTypeInfo API call. Arí can also use
this to give us more information, that can help us finding out what is
actually going wrong.
Here's the patch.
odbcconn.pas:
-
Michael Van Canneyt wrote:
Looking in the ODBCConnection, I would suppose that the DB2 Timestamp is
translated to SQL_TYPE_UTCDATETIME:
SQL_TYPE_UTCDATETIME:FieldType:=ftUnknown;
SQL_TYPE_UTCTIME: FieldType:=ftUnknown;
As you can see, they are not recignized by the ODBC
I created a Lazarus project to do a single browse
in DB2 table using DBNavigator and DBGrid. During
tests I used a DB2 table that didn't have columns
with DB2 TIMESTAMP type. Early today I modify the
SQL property of the TSQLQuery to another DB2
table that has a column with the type TIMESTAMP.
Wow, and I thought that DB2 wasn't supported at all...
Where did you get the DB2-component from? Since it's a problem with that
component, which has nothing to do with fpc/lazarus
On Fri, 2006-03-24 at 12:05 -0300, Arí Ricardo Ody wrote:
I created a Lazarus project to do a single browse
in
I take the component from Lazarus 0.9.12 SQLdb
repository after install sqldblaz package (I think, I'm not sure...) :-|
[ ]
At 12:19 24/3/2006, you wrote:
Wow, and I thought that DB2 wasn't supported at all...
Where did you get the DB2-component from? Since it's a problem with that
I'm pretty sure that sqldb does not support DB2
On Fri, 2006-03-24 at 12:45 -0300, Arí Ricardo Ody wrote:
I take the component from Lazarus 0.9.12 SQLdb
repository after install sqldblaz package (I think, I'm not sure...) :-|
[ ]
At 12:19 24/3/2006, you wrote:
Wow, and I thought that
On Fri, 24 Mar 2006, Joost van der Sluis wrote:
I'm pretty sure that sqldb does not support DB2
And via ODBC ?
Michael.
_
To unsubscribe: mail [EMAIL PROTECTED] with
unsubscribe as the Subject
archives at
I'm pretty sure that sqldb does not support DB2
And via ODBC ?
Offcourse, stupid of me. That could be the case.
But then, the fieldtype HREG_DIVDD doesn't sound as a odbc-fieldtype to
me.
Arí Ricardo Ody can you confirm that you are using ODBC?
--
Met vriendelijke groeten,
Joost van
As I explain in the first e-mail about this
matter, HREG_DIVDD is a TIMESTAMP DB2 field type.
[ ]
At 13:36 24/3/2006, you wrote:
I'm pretty sure that sqldb does not support DB2
And via ODBC ?
Offcourse, stupid of me. That could be the case.
But then, the fieldtype HREG_DIVDD doesn't
On Fri, 24 Mar 2006, Arí Ricardo Ody wrote:
As I explain in the first e-mail about this
matter, HREG_DIVDD is a TIMESTAMP DB2 field type.
(I received a screenshot in private)
Sounds like the error message is formatted wrong:
Unknown field type: HREG_DIVDD
Ricardo, it is not quite clear;
19 matches
Mail list logo
