Vista - Method '~' of object '~' failed

A VB6 program I wrote accesses the AD and fails with

Method '~' of object '~' failed

on a set of PCs of ONE particular customer. Other customers don't seem
to have problems with that.

I googled and found that this might have to do with the MDAC version
differing between my development machine and the customers machine. So I
asked the customer to run the component checker, which I did, too.

I found we're both using the (apparently) correct version MDAC 2.8 SP1
ON WINDOWS XP SP2. The details of his XML-report showed that a few files
on the customers machine are in a slightly newer version (me:
2.81.1117.0, his: 2.81.1128.0 xpsp_sp2_gdr.061226-0034).

Question remains: I don't see how the MDAC version could have caused this.

Anyone got another idea what I could tell the user to try?

Thanks in advance!

Regards,
T.

T. Valen wrote:Maybe try asking in a VB group? :-)

vbscript <> VB

Also, when you post to the VB group, show at least the line of code that
raises this error ... although a little context won't hurt.
In the meantime, you also might want to try perusing the results of this
google search:
http://www.google.com/search?sourcei...e%27+failed%22

--
HTH,
Bob Barrows

Bob, thanks for your - ljhwuohasuh - posting.
I may be wrong, but I thought the letters VB in this group name would
stand for the same letters that VB alone stand for.
Furthermore I believe the issue is probably reproducible with VBS.

Not really.

If you demand for it:

Set oRecordSet = CreateObject("ADODB.Recordset")
Set oConnection = CreateObject("ADODB.Connection")

Set oAD = GetObject(Provider) 'Determine the global catalog path
For Each oGlobalCatalog In oAD
strADsPath = oGlobalCatalog.ADsPath 'get last one
Next
oConnection.Provider = "ADsDSOObject" 'Initialize the ADO object
oConnection.Open "ADs Provider" 'The ADSI OLE-DB provider

'Create the search string

strQuery = "<" & strADsPath & _
">;(&(objectclass=computer)(samaccountname=" & sUserName &
"$));samaccountname,cn,distinguishedName;subtree"


(with strQuery =
<GC://domain.de>;(&(objectclass=computer)(samaccountname=D1137$));samaccountname,cn,distinguishedName;subtree)

What else would you need what's not already said?
Executing the query results into the mentioned error on some machines.

Thank you for believing that the idea the issue might have to do with
MDAC is based upon my own skills of debugging MS ADO internals. I'm
afraid this isn't so. I was just following the exact search reaults that
google gave me.

T. Valen wrote:Oooh! What's "ljhwuohasuh"? Nothing bad, I hope ...
My turn to go to google ...
Relevance? :-)
Maybe, maybe not.
I'm not sure why you are trying to shoehorn this into a vbs issue. Why
not simply post to a VB group and stop wasting time? Do you want to get
an answer to your question or argue about where the question belongs?
:-)
I'm not trying to reprimand you: I'm just saying you will be more likely
to encounter someone who can answer your question in a VB group.No ... really! :-)
They are not the same, beyond some of the syntax used ... really, that
is the only place where they are similar. Different runtime engines,etc.If "demand" is equivalent to "request", then yes, I demanded it :-)

<snip>Well, I "demanded" to see _the_ line of code that threw the error. By
"context", I meant a little context around the line of code: meaning a
few of the lines leading up to the line that throws the error rather
than simply just the line itself. You did that without realizing what I
was asking for, so I congratulate you. Many would have either posted the
single line of code that I asked for ... or worse: posted 2000 lines of
code just to make sure the lines causing the problem were included.

Do you use oRecordSet.Open or set oRecordSet =oConnection.Execute to run
it? Just in case it makes a difference to the person who actually has
the answer for you.
<snip>good one :-)

I'm afraid I have not encountered this error so I am not going to be of
any help beyond providing commiseration ... and I really do sympathize:
dll Hell is .... well ... Hell!

--
HTH,
Bob Barrows

> Oooh! What's "ljhwuohasuh"? Nothing bad, I hope ...

No. Could have been "piugpiqwipguz !!!!", too. It's what I am typing in
when I shouldn't use bad words. ;-)

Just make a game of it and make it an acronym for something that pleases
you. Start with something easy like: "disafg" (for example: "Damn, I'm
such a funny guy!")

Your parents were lawyers, weren't they? ;-)

Because I know of active participants in this group that know what
they're talking about. That's priceless and can't be found everywhere on
the net! ;-)

I'm going to do that.

But I'll come back to you and tell you the results when I'm done with
this! ;-)

Well, yes, let me put this way: "Do you want to answer my posting or
argue where the question belongs?" ;-)

The point is that the issue itself has nothing to do with VB or VBS
itself but is a ADO-problem. Where should I post it? A VB-board is as
good or bad as a VBS is. I'll go ahead and try
microsoft.public.vb.database.ado but I'm not sure that that one is better.

Sorry, I'm no native English speaker. I meant "request" and I realized
that "demand" means something different.

Damn, I just found I missed to post this line in my last posting. Sorry:

Set oRecordSet = oConnection.Execute(strQuery) 'Execute the query

But thank you for that. It feels so good. ;-)

T. Valen wrote:Now that is a good point. microsoft.public.data.ado springs to mind ...
that is, if it is an ADO problem. You expressed doubts about that
yourself.
Right - you might want to crosspost to .general as well, just in case it
really isn't an ADO issue.

--
HTH,
Bob Barrows