Re: ActiveX error in odd location...
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Tue, 15 Apr 2008 20:10:56 -0500
"Ron B." <wednesdaytennis@xxxxxxxxx> wrote in message
news:d01b19e3-2d41-46c0-a359-aa4d36598d53@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Okay, so I have a VB6 application that is using "disconnected ADOrecordset
recordsets" to store and process data. It works fine on a ton of
computers, but I have a new client that can't get the application to
run. Plus this problem is occuring on two different computers at the
client location.
My code is basically as follows...
Dim rsResult As ADODB.Recordset 'dim variable
Set rsResult = New ADODB.Recordset 'create new
recordsetrsResult.Fields.Append "RecID", adInteger 'append fields to
location for disconnected recordsetrsResult.CursorLocation = adUseClient 'set the cursor
type for disconnected recordsetrsResult.CursorType = adOpenStatic 'set the cursor
'open the recordsetrsResult.Open
I get an error "429 ActiveX Component can't create object".
The odd part is that I do NOT get the error on the "Set rsResult = New
ADODB.Recordset" line.
I get the error on the "rsResult.Open" line.
I have confirmed that the client is running MDAC 2.8. Any ideas what
might be going on here for ONE client when it runs fine for 5-6 other
clients?
Thanks for your help!!!
That error is always accurate. (usually <g>) There are mismatched components
on the target/problem boxes compared to the components that App was compiled
with.
The 'mystery' is caused by the fact that there is a component registered on
the machine that supports the ADODB.Recordset Interface, but doesn't support
the ProcID provided by the rs.Open.
You are going to have to figure out which components don't match. Do you
have access to those boxes? How and what you can do will depend on that.
Are the users reasonably technical? You or they can run the MS MDAC
Compatibility utility. You can download the ProcessMonitor from
SysInternals. etc. Re-install the appropriate MDAC for their machine, etc.
Good hunting. <g>
-ralph
.
- References:
- ActiveX error in odd location...
- From: Ron B.
- ActiveX error in odd location...
- Prev by Date: Re: ActiveX error in odd location...
- Next by Date: Forward-only recordsets
- Previous by thread: Re: ActiveX error in odd location...
- Next by thread: Forward-only recordsets
- Index(es):
Relevant Pages
|
|
