Re: Using TADODataset with DB2
From: Arnie Mauer (xxx_at_nowhere.net)
Date: 03/11/04
- Next message: F.Stockmann: "Problems with Select Querries and TBetterAdoDataset"
- Previous message: Pavel: "Re: ADOdataset loses two rows if processor is two busy (asynchronous)"
- In reply to: Emile Cronje: "Using TADODataset with DB2"
- Next in thread: Emile Cronje: "Re: Using TADODataset with DB2"
- Reply: Emile Cronje: "Re: Using TADODataset with DB2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 11 Mar 2004 11:46:07 -0500
"Emile Cronje" <emile@mosaicsoftware.com> wrote in message
news:405068cb$1@newsgroups.borland.com...
>
> Hi
>
> I am using a TADODataset component with CursorLocation = clUseServer and
CursorType = ctDynamic.
>
> When connected to a DB2 database, I set the CommandText property of the
TADODataset component to something simple, like 'select * from table_x'.
>
> When I call TADODataset.Open, I get the following message:
> 'Multiple-step OLE DB operation generated errors. Check each OLE DB status
value, if available. No work was done'
That's one of my *favorite* error messages.
>
> Any ideas, please? Does DB2 support the notion of server side cursors?
Yes, it does. What driver are you using? DB2 OLEDB or MSDASQL over the DB2
ODBC driver? IBM can't seem to produce a decent OLEDB driver.
Try using a bidirectional cursor type. We've seen this error most when
there's a datatype mismatch or typo in a column or table name - although
your statement seems pretty simple. What platform is DB2 on?
- Arnie
>
> Thanks
- Next message: F.Stockmann: "Problems with Select Querries and TBetterAdoDataset"
- Previous message: Pavel: "Re: ADOdataset loses two rows if processor is two busy (asynchronous)"
- In reply to: Emile Cronje: "Using TADODataset with DB2"
- Next in thread: Emile Cronje: "Re: Using TADODataset with DB2"
- Reply: Emile Cronje: "Re: Using TADODataset with DB2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
