Re: "No such interface supported" error on Catalog.Create and Connection.Open

Hi,

These problems get very complex. One of these KB articles might help.

http://support.microsoft.com/default.aspx?scid=kb;en-us;303528

http://support.microsoft.com/default.aspx?scid=kb;en-us;307255

--
Richard
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net

"Preben Nyeng" <pny@xxxxxxxx> wrote in message
news:uy3Iy8kTGHA.2444@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for your answer. Does the odbcjet32.dll have any influence when I
don't use ODBC? I use the OLE DB driver for JET through ADO.
Regards, Preben

"Richard Mueller" <rlmueller-NOSPAM@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OElG0JeTGHA.4300@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

I believe your problem is not MDAC, but rather the jet driver
(odbcjt32.dll). I have found computers where this driver exists, but is
misconfigured. In ODBC Data Source Administrator (Settings, Performance
and Maintenance, Administrative Tools) on the "Drivers" tab you may be
lacking the required driver setting (even though odbcjt32.dll exists). I
cannot remember the fix we used. It may have been to reinstall the jet
drivers. If someone else doesn't reply, search on access jet driver
odbcjt32.dll.

--
Richard
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net

"Preben Nyeng" <pny@xxxxxxxx> wrote in message
news:uIonCPcTGHA.4300@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have a problem with an app using ADO and ADOX to access MDB files
using JET 4.0
The app runs well on anything from Windows 95 to XP, but on very few
machines the app will fail with the error mentioned in the subject.
I have seen it about 5 times on W2K with MDAC2.5, in each case an update
to the latest MDAC solved the problem.
But now I am stuck with an XP SP2 (MDAC2.8), because no newer MDAC is
available, and therefore an update is impossible.
There are 2 cases of the error:
1. When trying to open an existing DB (named OldDB). The ADO Connection
object is initialized with:
.Provider = "Microsoft.Jet.OLEDB.4.0"
.Mode = adModeReadWrite
.Open("OldDB") fails.
2. When trying to create a new DB (named NewDB), using the ADOX Catalog
object:
.Create("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=NewDB")

Any hints on how to solve the problem will be appreicated.
Thanks in advance,
Preben Nyeng








.

Relevant Pages

  • Re: using ado drivers with 64 bits software
    ... knowledge there won't be any 64 bit driver for JET; ... the use of the MDB file format as the backend should only be ... This email account is my spam trap so I ...
    (microsoft.public.data.ado)
  • Re: "No such interface supported" error on Catalog.Create and Connection.Open
    ... I use the OLE DB driver for JET through ADO. ... In ODBC Data Source Administrator (Settings, ...
    (microsoft.public.data.ado)
  • Analysis Services Tutorial - Writeback Capability
    ... Switched the OLE DB driver from ODBC to Jet 4.0 based on not being able to write-enable either of the cubes in the tutorial with the ODBC driver. ...
    (microsoft.public.sqlserver.olap)
  • Re: 64-bit Version of Microsoft Access?
    ... The real problem is the absence of a 64 bit JET ODBC driver: ... the web service of Windows can run in either ...
    (microsoft.public.access.dataaccess.pages)
  • Re: MsAccess and IA64
    ... I noticed that there is no 64 bit Jet Driver available ... 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local ... I am thinking there might be a way to install a 32 bit version of the ...
    (microsoft.public.dotnet.languages.csharp)