Don Orrell
|
| Posted: 08/13/2001, 7:53 PM |
|
I am working with a client who is running DB2 on an AS/400. Using stright
SQL, you have to place the libray in front of the table. ex. Select * from
Library.Table.
My connection string is "Provider=MSDASQL.1;Driver={Client Access ODBC
Driver (32-bit)};System=XXX,XXX,XX,XX", I have to use the ODBC driver
because many of the field names contain the "#" character and IBM's ODBC
driver is the only thing I find that works.
My question is "How do I tell CodeCharge what Library to use?" I don't
want to use SQL statements on every screen. Can the connection string
handle DBQ=? Anyone who knows DB2 connecting to an AS/400 using OLE DB,
please help.
Thanks.
Don Orrell
dorrell@favoritenurese.com
|
|
|
 |
Nadeem
|
| Posted: 08/21/2001, 2:55 AM |
|
Hi Don,
I am wondering what version of AS/400 you are dealing with? I did use Client
Access for AS/400 E Series, and I did mention my library while configuring
ODBC client, later I don't have to mention library names in SQL statements
anymore. However, I don't have to use "[" and "]" in my SQL statements as
these are not welcomed by DB2 SQL.
For your information, I have successfully completed a project using CC while
AS/400 DB2 was on backend. I am not an AS/400 guy but my colleague who
configured the Client Access faced no problem. Perhaps it was AS400E series.
Nadeem
"Don Orrell" <dorrell@sound.net> wrote in message
news:9la3qc$378$1@news.codecharge.com...
> I am working with a client who is running DB2 on an AS/400. Using stright
> SQL, you have to place the libray in front of the table. ex. Select *
from
> Library.Table.
>
> My connection string is "Provider=MSDASQL.1;Driver={Client Access ODBC
> Driver (32-bit)};System=XXX,XXX,XX,XX", I have to use the ODBC driver
> because many of the field names contain the "#" character and IBM's ODBC
> driver is the only thing I find that works.
>
> My question is "How do I tell CodeCharge what Library to use?" I don't
> want to use SQL statements on every screen. Can the connection string
> handle DBQ=? Anyone who knows DB2 connecting to an AS/400 using OLE DB,
> please help.
>
> Thanks.
>
> Don Orrell
>dorrell@favoritenurese.com
>
>
>
>
|
|
|
|
Don Orrell
|
| Posted: 08/26/2001, 8:02 PM |
|
The DB2 version on the AS/400 is 4.4. It appears the DBQ=Library is
working. Doing more test to be sure. I just wish I could cut out the ODBC
layer all together and use stright OLE DB. Is seems very slow the way I am
currently connecting to the AS/400.
Thanks for responding.
Don Orrell
"Nadeem" <nadeem@univer.com> wrote in message
news:9ltb60$7q4$1@news.codecharge.com...
> Hi Don,
>
> I am wondering what version of AS/400 you are dealing with? I did use
Client
> Access for AS/400 E Series, and I did mention my library while configuring
> ODBC client, later I don't have to mention library names in SQL statements
> anymore. However, I don't have to use "[" and "]" in my SQL statements as
> these are not welcomed by DB2 SQL.
>
> For your information, I have successfully completed a project using CC
while
> AS/400 DB2 was on backend. I am not an AS/400 guy but my colleague who
> configured the Client Access faced no problem. Perhaps it was AS400E
series.
>
> Nadeem
>
>
> "Don Orrell" <dorrell@sound.net> wrote in message
>news:9la3qc$378$1@news.codecharge.com...
> > I am working with a client who is running DB2 on an AS/400. Using
stright
> > SQL, you have to place the libray in front of the table. ex. Select *
> from
> > Library.Table.
> >
> > My connection string is "Provider=MSDASQL.1;Driver={Client Access ODBC
> > Driver (32-bit)};System=XXX,XXX,XX,XX", I have to use the ODBC driver
> > because many of the field names contain the "#" character and IBM's ODBC
> > driver is the only thing I find that works.
> >
> > My question is "How do I tell CodeCharge what Library to use?" I don't
> > want to use SQL statements on every screen. Can the connection string
> > handle DBQ=? Anyone who knows DB2 connecting to an AS/400 using OLE DB,
> > please help.
> >
> > Thanks.
> >
> > Don Orrell
> >dorrell@favoritenurese.com
> >
> >
> >
> >
>
>
|
|
|
|
|
