Link to home
Start Free TrialLog in
Avatar of clutcher3
clutcher3

asked on

Method ' open ' of object '_Connection' failed

This is the scenario:

Xp Professional and VB6 SP4. An application of mine that has run for months. Source in error follows.

Set ConnAS400 = New ADODB.Connection
ConnAS400.ConnectionString = "DSN=AS400;UID=PC;PWD=S"
ConnAS400.Open

This application query a lot of different ODBC sources (including IBM Client Access Express) and analyze and write results in a xls file.

For reason due to secondary hd swap on my pc, IBM Client Access V4R4M0 seems to stop working. So I upgrade it to V4R5M0.

After this I get the error in the title usinig *ANY* ADO ODBC connection in VB or by a compiled exe. This and other application of mine still continue to work fine on any other pc. But I cannot develop anymore.

Searching the web I found that XP has MDAC 2.7 inside and so no rollback is allowed and reinstalling 2.7 doesn't fix. VB6 SP5 did not fix either.

A person in NG says that he work out this issue disinstalling Ca and reinstalling sp2 on w2k... on w2k, and I have XP.

A part from waiting for next week Xp SP1 has anyone any suggestion?

(I start from 200 but I think this is quite hard and I will increase)

TIA

Marco
Avatar of clutcher3

ASKER

Tnx for your attention. I did not previously find those articles but they do not resolve, even the last one; the other one confirms my impression that applying MDAC 2.7 (or any other version) on XP reports a success but does really nothing.

I found also this one:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q309519&

I forgot to say that Component Checker says it's all fine (it gives the same result of an healthy pc) and neither manually registering msado15.dll and odbc*.dll cleans the problem.

Increasing points.
XP SP1 in italian is still unavailable and my users want the report...
Still no news from MS. Point increased.
>>IBM Client Access V4R4M0 seems to stop working. So I upgrade it to V4R5M0

Have you tried installing the drivers and mdac on a new XP system?  What if you downgrade the AS400 drivers back to a working version that you know works.
>Have you tried installing the drivers and mdac on a new
>XP system?  

On a new XP system with any IBM CA version works fine, as it was on my pc prior to the problem.

>What if you downgrade the AS400 drivers back to a
>working version that you know works.

The matter is on *my* computer, no workaround (including disinstalling and reisytalling IBM products V4R4 or V4R5) seems to fix and, in fact, I can't develop.

An installation of a new XP upgrade, that overlap mine without losing my configuration and programs, resolved the bug.

For administrators: what can I do in this case? Give points to aeklund with a low grade?

ASKER CERTIFIED SOLUTION
Avatar of modulo
modulo

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Points refunded and moved to PAQ.

clutcher3

A low grade is not a good idea. The help aeklund provided might not have helped you, but it wasn't bad at all. Many experts rather not take points than getting a low grade. If you want to reward him, you can always post a 'dummy' question with a title "Points for aeklund" and a body "For your help with ..." in this topic area.

** Mindphaser - Community Support Moderator **
Hmmm ... tooo slow ....
Yep, beaten by modulo the benjamin moderator <LOL>