Make sure the other stations have equal or newer MDAC's.
On your development computer, check the version of ADO that you referenced
and make sure that the clients are running that version or greater. ADO is
backward compatible, no guarantee that it is forward compatible.
Check
http://www.microsoft.com/data for the latest Microsoft data access
components.
"Daniel Fisherman" <dfisherman@optonline.net> wrote in message
news:a960c6c6.0310230549.25a647a1@posting.google.c om...[color=blue]
> The statement that begins with o.open in the procedure below raises
> either a "Type Mismatch" error or a "Method ~ of Connection object
> failed" error on SOME workstations. Does anyone have a clue as to
> what might be wrong? Could the Jet OLEDB driver be at fault here?
>
> Any help would be appreciated.
>
> Dan Fisherman
>
>
>
> Private Sub Command1_Click()
> Dim o As ADODB.Connection
>
> On Error GoTo ProcError
> Set o = New ADODB.Connection
> o.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
> Files\MacPac\Personal\ci.mdb"
> Exit Sub
> ProcError:
> MsgBox Err.Number & ": " & Err.Description, "AGG CI Test"
> Exit Sub
> End Sub[/color]
