RE: ODBC to AS/400 using Visual Basic 4.0

Don,

Yes, unfortunately, using ODBC and a DSN you can only open *FIRST.  With ADO
you can open any member, as well as invoking commitment control.

That isn't to say it can't be done, but if it can, I don't know how.

One workaround might be to build a logical that points to the member you want to
access, and use the logical.  ODBC doesn't really differentiate between LF and 
PF,
so you should be able to get at your data that way.

CAExpress is supported from V3R7 on up, but I understand what you're running 
into.
What you really need is a data provider that supports ADO for the iSeries.  I 
prefer
the Client Access Express ADO provider, but ASNA's data gate suite comes with a
good provider, too.  Even if you get that, you still need a development 
environment
that supports ADO, which VB 4 doesn't.

Another option would be to use sockets.  If memory serves, VB4 enterprise will 
let
you develop winsock clients.  Sockets are faster than hell, don't have the 
overhead of
ODBC, and would let you get at specific members.  What you do is write a socket
server in RPGIV that runs on the iSeries, and a client in VB (or whatever) that 
runs
on your PC.  The client talks to the server through a socket on a given port 
(which
you define). No client access or other ADO required.  Of course, I'm assuming 
your
iSeries is running TCP/IP.

Scott Klement has an excellent tutorial on how to use sockets, which you can 
find
here:

http://klement.dstorm.net/rpg/socktut/

Can't help you with the boss thing.  If you worked for me, you'd be encouraged 
to try
new things.  I get a better programmer, you get to be a better programmer, the
business gets more robust applications, everybody wins.  I guess some people 
just
don't see it that way....

Good luck!

--Chris



> From: "Fisher, Don" <Dfisher@roomstoreeast.com>
> To: "'midrange-l@midrange.com'" <midrange-l@midrange.com>
> Subject: RE: ODBC to AS/400 using Visual Basic 4.0
> Date: Fri, 13 Sep 2002 08:42:23 -0400
> Reply-To: midrange-l@midrange.com
>
> Yes, I believe I'm using RDO.  I create workspace, database, and
> record set objects.  Then I assign the desired AS/400 file to the
> database object using the OpenDatabase method of the workspace and
> open the file using the OpenRecordset method of the database object.
>
> Taking your advice, I attempted to open the file in Access and
> achieved success, but only after changing the naming convention for
> the ODBC driver to "SQL".  However, Access would not recognize the
> multiple members in the file.  Perhaps that is a limitation of ODBC?
>
> So I went back to my program and changed the code to use the SQL
> naming conventions and now it works.  At least it will open the record
> set, but only against the first member.  Is there no way to make it
> open a specific member?
>
> <long deep sigh>
> Your other recommendations sound very reasonable, but I do not have
> Client Access Express here as our primary production machine is on
> V4R1 and not likely to be upgraded.  We do have a V4R5 box for our
> Lawson package, though.  Would that help me?
>
> I am also highly unlikely to convince my boss we need to invest in VB6
> or VB.net.  The only reason I've been allowed to work with VB 4.0 is
> because we already had it.  At least it's the "Enterprise" version.
>
> Thanks for your help.
>
> Donald R. Fisher, III
> Project Manager
> The Roomstore Furniture Company
> (804) 784-7600 extension 2124
> DFisher@roomstoreeast.com
>