ADO OLE DB connection to iSeries - V5R2

[giger]

Hi,

First post here and i'm hoping you guys can help me out.

I recently distributed a VB app that was connecting to an AS400 that was using V5R1 OS. All was well until we upgraded to V5R2. All users had client access upgraded and ever since then, I have had 3 people (out of 10) who can no longer connect. The failure occurs as soon as the .open of the ado connection is issued. I'm using OLE DB (which seems to be the best connection method). Rolling back client access to V5R1 allows them to successfully connect again.

My question is how can I ensure a reliable connection each time under V5R2?!

Using VB6, SP5 - developed on Win 2000 using ADO 2.7 library. Users on XP OS using MDAC 2.7

Has anyone experienced similar?

TIA

Giger

[brucevde]

Assuming all things are equal., all 10 people are using/have the same programs, OS, versions etc..

If 7 out of 10 people can connect using the new version, then chances are the upgrade failed on the other 3. The usual culprit is one or more dll's were not registered properly.

Have you checked the installation log files, help files etc..?
Verified the correct installation of every Dll - version and registry entries?

[giger]

Hi,

To set users up, we basically built one machine up, installed and tested all software. Then we took an image of the harddrive to build the other PCs.

One of our PC engineers performed the Client Access upgrade and no anomolies were reported.

I'll have a dig around tomorrow but we have tried completely un-installing client access (and the VB app in question) and installing again. - No luck

I have now updated one user to use a DSN connection instead of OLE DB and connection was successful. However I am keen to steer clear of this approach. Would ideally like to get OLE DB working again.

Thanks for the input though, any other contributions welcome.