Web Development

General discussion


using the dll as odbc driver

By sanilveeravu ·
I have the dll file (odbc driver) to connect to AS400. Is it possible for me to write a VB code to connect to AS400 just by using this or should I install the whole software which contains a lot of other features.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by hmertens In reply to using the dll as odbc dri ...

That depends...

Posession of the "software" (dll and the rest) usually under licence. I'm presuming that you acquired the whole ODBC driver bundle (as part of another application?) software and that you are not just "borrowing" the specific DLL for its specific functionality. With that out of the way... You may not have a legal right use the ODBC component outside of the software that actually uses it. And unless they have may specific exclusions to using the ODBC driver outside of their application (there may be code involved) and can see why you can leverage all components that are installed on a system.

Did the install package that added this ODBC functionality actually run a third-party setup (the third-party being the actual developer of the ODBC component) for installing that part? There may be support DLLS/resources that this DLL will need to work (EBCDIC to ASCII codepage translation tables for one, comes to mind). Examine the installation package and see if you can see the seperation of the OBDC stuff from the rest. Look for "readme's" that may have come from the component provider.

Adding to the ODBC environment can be tricky without using the proper install package. Have you tried "registering" the DLL in a clean system (without all of the other stuff) (regsrv32.exe)? Included it in VB project? Try checking out the DLL in the object browser then.

Can you check out the properties of this DLL - who is the "company" that developed it. See if they have a website - sometimes (not often though), the ODBC drivers are available as seperate downloads.

This seems to be one of those "You'll have to try it" situations.

Could you provide more details about the DLL; version, filename, internal name, company, etc...?

Collapse -

by hmertens In reply to

Your directly emailed comment stated "...i have tried using regsvr32 but it replied with the load library not able to find the module."

Registering a DLL (into the registry hive) requires a pathname be stated if you are not sitting on top of the DLL in the same directory (it _might_ also work if the .DLL is in the search path, but don't quote me on that one). The full pathname is part of the registration process as well. More than likely you are already on top of this take on the error message (or?).

There is a possiblility that use need to pass along some command line switch to the DLL via the /i:... directive of regsvr32.

Finally, are there a series of DLLs that have to be installed in a specific order? Can you scan any .INI or similiar setup control files to locate either /i: regsvr32 directives, or a specific install order of DLLs (maybe difficult if they are in binary files, but a file viewer should still be able to locate ascii strings such as file names).


Collapse -

by hmertens In reply to

In your direct email reply, you state that s/w is licensed for only 4 PCs - which I presume are already in use, but not on the machines where you hope to deploy the specific ODBC/VB solution?

The product that provides your ODBC is from IBM - Client Access Express (yes?). IBM now refers to this technology as "iSeries Access for Windows", and now support an OLEDB programmability vs ODBC.

Have you scanned the URL


for any info specific to your situations. From my scan of this site, the only sell these connectivity products under license.


Related Discussions

Related Forums