Connecting to iSeries with MS Access

[Chevylover54]

We have been using ODBC connections that are in the registry of the computer. However these connections aren't in by default so when a new user uses the Access program or when a current user goes to a different computer, we have to send them the batch program to put the ODBC hooks on that machine.

We want to get around that by using Pass-Through queries and the ODBC connection string. What we have got to work is this:

ODBC;FILEDSN=n:\PND43851.DSN

Then we put a DSN file in that location and the program connects using that DSN. The DSN file looks like this:

[ODBC]
DRIVER=iSeries Access ODBC Driver
UID=
SIGNON=2
CONNTYPE=2
DESC=iSeries Access ODBC
SQDIAGCODE=
DATABASE=
QAQQINILIB=
PKG=QGPL/DEFAULT(IBM),1,0,1,0,512
TRACEFILENAME=C:\
SORTTABLE=
LANGUAGEID=ENU
XLATEDLL=
DFTPKGLIB=QGPL
DBQ=RIDTA385
SYSTEM=PND43851

We want to take it one step further and put all the info in the ODBC Connection string but we haven't had any luck. We have tried many variations of the following:

ODBC;Driver={iSeries Access ODBC Driver};System=PND43851;

When we use ODBC;Driver={iSeries Access ODBC Driver}; an ODBC connection screen comes up like you are at your control panel in windows and go to ODBC connections.

If we use ODBC;Driver={iSeries Access ODBC Driver};System=PND43851; we get error (-7778) which is "there is no message for this error".

We have tried all kinds of combinations of "'s and ;'s and any other thing we can think of, including using all the fields in the above DSN in that line.

Is this even possible? If so can someone tell me where my error is?

Thanks.

[NeoPa]

You've obviously tried the 'Trial & Error' approach with some intelligent guesswork.
The other thing I'd try is to find a manual (hard copy or web based - doesn't matter which) to see if that can tell you.
The last possibility I can think of is to try the vendor's web site. Maybe they even have forums there for technical questions.
I'm sure it will be specific to the product. I did it to my SQL server by linking a table then studying the .Connect property of the linked table (with some Trial & Error). My other ODBC server (EasySoft) had quite different parameters set.