Re: Error 429 when opening a disconnected recordset
- From: "Richard Mueller" <rlmueller-NOSPAM@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 3 Apr 2006 11:50:41 -0500
I thought only MDAC was required. I can run VBScript programs that use
disconnected recordsets on Windows 95 clients.
If this is a VB6 program could you be referencing a version of ADO not on
the client? If your program is not installed with something that would
upgrade MDAC, it might help to reference the oldest version of ActiveX Data
Objects available.
--
Richard
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
"Andy DF" <nospam@xxxxxxxxxx> wrote in message
news:4430d3b7$0$29116$5fc30a8@xxxxxxxxxxxxxxxxxx
(This was previously posted on microsoft.public.vb.databse.ado, sorry for
multiposting, I guess I posted in the wrong NG.)
The following code creates and opens a disconnected ADODB.Recordset.
On some machines I get an error 429 "ActiveX component can't create
object" when the Recordset.Open statement is executed.
This has happend on Win ME and on Win XP.
Does anyone know what could be the source of the problem?
TIA,
Andy
Private Sub pTest1()
Dim rs As Recordset
On Error GoTo ERR_OUT
Set rs = New Recordset
rs.Fields.Append "TestField", adBoolean
rs.Open ' Error 429 HERE!!! WHY???
' Ok
MsgBox "Test #1: OK", vbInformation
' Clean up
rs.Close
Set rs = Nothing
Exit Sub
ERR_OUT:
MsgBox Err.Description & vbCrLf & Err.Number, vbExclamation
Err.Clear
End Sub
.
- References:
- Error 429 when opening a disconnected recordset
- From: Andy DF
- Error 429 when opening a disconnected recordset
- Prev by Date: Re: are there limitations of SQL used in text driver via ADO
- Next by Date: Is it possible to repaire damaged MDAC/ADO on XP with SP2 ?
- Previous by thread: Error 429 when opening a disconnected recordset
- Next by thread: Re: are there limitations of SQL used in text driver via ADO
- Index(es):
Relevant Pages
|
|
