What to use instead of SQLDataAdapter?

  • Thread starter Thread starter coleenholley
  • Start date Start date
C

coleenholley

We don't use a connection to a SQL Server, and therefore when I try paging, the simple way to do it using a SQL DataAdapter does not work. Is there an alternative for this, such as for an ODBCDatatAdapter? I looked through the available Objects and could not find anything similar for and ODBC Connection (we connect to a DB2 database using RPC's written in COBOl and create Class modules to connect to the CICS region...it is not pretty) Does anyone have any suggestions for a replacement for the DataAdapter? TIA...

Coleen
 
What server are you using?

We don't use a connection to a SQL Server, and therefore when I try
paging, the simple way to do it using a SQL DataAdapter does not work. Is
there an alternative for this, such as for an ODBCDatatAdapter? I looked
through the available Objects and could not find anything similar for and
ODBC Connection (we connect to a DB2 database using RPC's written in COBOl
and create Class modules to connect to the CICS region...it is not pretty)
Does anyone have any suggestions for a replacement for the DataAdapter?
TIA...
Community Website: http://www.dotnetjunkies.com/newsgroups/
 
We connect to a Mainframe not a particular server. We use CICS to establish the connection. Unfortunately, I don't know that much about the connection process, except that the code in the Class Modules to connect is UGLY! I didn't write it, and I don't understand most of what was written, so it's really a difficult process to try and troubleshoot the paging errors. Basically, the If Not Page.IsPostBack doesn't seem to work for us...the same set of data is returned each time you select a page number, then after switching through the pages, everything disappears - no datagrid, no labels, nothing...weird! Any help is appreciated :-) Coleen
 
If you are not connecting to SQL Server, then you should not be using any of
the classes in the SQLClient namespace, instead use the classes in the OLEDB
namespace. You could then use the OLEDB.DataAdapter.


We don't use a connection to a SQL Server, and therefore when I try
paging, the simple way to do it using a SQL DataAdapter does not work. Is
there an alternative for this, such as for an ODBCDatatAdapter? I looked
through the available Objects and could not find anything similar for and
ODBC Connection (we connect to a DB2 database using RPC's written in COBOl
and create Class modules to connect to the CICS region...it is not pretty)
Does anyone have any suggestions for a replacement for the DataAdapter?
TIA...
Community Website: http://www.dotnetjunkies.com/newsgroups/
 
Do you at least know what kind of database you are using? When you say
"mainframe" are you referring to UNIX or AIX or something else?

coleenholley said:
We connect to a Mainframe not a particular server. We use CICS to
establish the connection. Unfortunately, I don't know that much about the
connection process, except that the code in the Class Modules to connect is
UGLY! I didn't write it, and I don't understand most of what was written, so
it's really a difficult process to try and troubleshoot the paging errors.
Basically, the If Not Page.IsPostBack doesn't seem to work for us...the same
set of data is returned each time you select a page number, then after
switching through the pages, everything disappears - no datagrid, no labels,
nothing...weird! Any help is appreciated :-) ColeenCommunity Website: http://www.dotnetjunkies.com/newsgroups/
 
if this doesn't work there is an odbc.net assembly for download from
microsoft. i believe it comes standard in the framework v1.1 as the
system.data.odbc namespace, but you'll have to download it separately if you
are using v1.0.

you can find it here...

http://tinyurl.com/3c3dh

we've used it to connect to a btrieve backend and it's relatively reliable.
there are problems though mostly associated with provider compatibility, not
the classes themselves...

hope this helps,

jim




I'll try that...hope it works with our configuration :-) Thanks.
Community Website: http://www.dotnetjunkies.com/newsgroups/
 
* coleenholley said:
We connect to a Mainframe not a particular server. We use CICS to
establish the connection. Unfortunately, I don't know that much about
the connection process, except that the code in the Class Modules to
connect is UGLY! I didn't write it, and I don't understand most of what
was written, so it's really a difficult process to try and troubleshoot
the paging errors. Basically, the If Not Page.IsPostBack doesn't seem
to work for us...the same set of data is returned each time you select a
page number, then after switching through the pages, everything
disappears - no datagrid, no labels, nothing...weird! Any help is
appreciated :-) Coleen

Would be great if you break lines after 76 chacters.
Posted using Wimdows.net NntpNews Component - Posted from .NET's
Largest Community Website: http://www.dotnetjunkies.com/newsgroups/

Dumb web interface.
 
Back
Top