ODBC connect to AS/400

  • Thread starter Thread starter Greg Hopp
  • Start date Start date
G

Greg Hopp

We have an Access 2000 app that connects via ODBC to an
AS/400. We just got some XP machines and don't know how
to configure ODBC on XP to talk to the AS/400 correctly.
The XP machines have MDAC 2.5 which is required, but in
pre-XP, configuring an ODBC connection was different.

In the past, on NT 4.0, when we launched the app, it
would automatically create an ODBC entry called
WCARSBOT. All I had to do then was open that entry and
make a few changes and it would work.

With XP, the entry is no longer created and I don't know
how to create a new one from scratch.

Any help? Is there a better forum in which to post this
question?

TIA,

Greg H.
 
Greg Hopp said:
We have an Access 2000 app that connects via ODBC to an
AS/400. We just got some XP machines and don't know how
to configure ODBC on XP to talk to the AS/400 correctly.
The XP machines have MDAC 2.5 which is required, but in
pre-XP, configuring an ODBC connection was different.

In the past, on NT 4.0, when we launched the app, it
would automatically create an ODBC entry called
WCARSBOT. All I had to do then was open that entry and
make a few changes and it would work.

With XP, the entry is no longer created and I don't know
how to create a new one from scratch.

Any help? Is there a better forum in which to post this
question?
Click to expand...

If the app is/was creating an ODBC DSN automatically it had to be because
someone added custom code to do so. I can't think of any reason why such
code would work on NT 4 and not on XP. Are you sure the users have the
same authorities on the XP machines as they do on the NT machines?

Any reason you can't just create the ODBC entry manually? Are you using
IBM's Client Access driver or a third-party driver? (most of those stink).
 
If the app is/was creating an ODBC DSN automatically it
had to be because someone added custom code to do so.
Click to expand...
You are correct.
Are you using IBM's Client Access driver <snip>
Click to expand...
Yes we are. You hit the nail on the head. With XP, we
are using a new version of the Client Access ("CA")
driver. For whatever reason, the older NT machines with
the older CA automatically get the Client Access ODBC
driver when CA is installed. The newer version CA does
not appear to provide it. But I don't know whether that
was my SysAdmin's option or IBM's.

I have to check how to get IBM's CA ODBC driver and that
should fix our problem.

Thanks for pointing this out.

Greg
 
Back
Top