oopps, that was a typing mistake. the actual connection string reads
Provider=Microsoft.Jet.OLEDB.4.0;

----- Original Message -----
From: "Ken Schaefer" <[EMAIL PROTECTED]>
To: "ActiveServerPages" <[EMAIL PROTECTED]>
Sent: Thursday, August 15, 2002 12:32 AM
Subject: Re: Driver Error


> Hi,
>
> This is what you are using for the Provider name:
> Provider=microsoft.oledb.jet.4.0;
>
> Now look very closely at the one here:
> http://www.able-consulting.com/ado_conn.htm#OLEDBProviderForMicrosoftJet
>
> Notice there is a slight difference in the order of OLEDB and Jet
>
> Cheers
> Ken
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> From: "Zaid Abdur-Rahman" <[EMAIL PROTECTED]>
> Subject: RE: Driver Error
>
>
> : I don't believe the problem is with the sql statement since it executes
> : fine using a different connection string.
> :
> : -----Original Message-----
> : From: Robert Chartier [mailto:[EMAIL PROTECTED]]
> : Sent: Wednesday, August 14, 2002 6:03 PM
> : To: ActiveServerPages
> : Subject: Re: Driver Error
> :
> :
> :
> : response.write sql
> :
> : just before the line
> :
> : set rs = conn.execute(sql)
> :
> : then copy and paste that output to your database's sql query analyzer
> : and
> : try to run it
> :
> :
> :
> : At 05:45 PM 8/14/2002 -0400, you wrote:
> : >I implemented the OLEDB for Jet and I know get the following error.
> : Below is
> : >the connection string and error
> : >
> : >Provider=microsoft.oledb.jet.4.0;data source=c:\db.mdb
> : >
> : >error '80004005'
> : >Unspecified error
> : >
> : >This error happens at the point of executing an sql statement. Below is
> : an
> : >example of one of the statements
> : >sql = "SELECT * FROM temporary WHERE CustomerId='"&CustomerId&"' ORDER
> : BY
> : >item;"
> : >set rs = Conn.Execute(sql)
> : >
> : >Am I doing something wrong?
> : >
> : >
> : >
> : >----- Original Message -----
> : >From: "Nabil Al-Hage Ali" <[EMAIL PROTECTED]>
> : >To: "ActiveServerPages" <[EMAIL PROTECTED]>
> : >Sent: Wednesday, August 14, 2002 2:34 PM
> : >Subject: Re: Driver Error
> : >
> : >
> : > > In such a case the best thing to do is to redefine your DSN again
> : and make
> : >sure to use
> : > > the new driver for the new database system installed ( in your case
> : MS
> : >ACCESS 2000).
> : > >
> : > > if you are not obliged to use DSN connection ,try also DSNLESS
> : connection
> : >with OLEDB for
> : > > Jet(Direct connection).
> : > >
> : > > Nabil.
> : > >
> : > > > Hello All,
> : > > >
> : > > > I am occasionally getting the following error on my application
> : which is
> : > > > running on WinNT, IIS4, Access2000. It was running on Access 97
> : and I
> : >was
> : > > > told to upgrade the DB to Access 2000 to stop the error. But, I am
> : still
> : > > > getting it. Stop/start iis stops the error.
> : > > >
> : > > > Any ideas?
> : > > >
> : > > > Line 3 is my connection string "driver={microsoft access driver=
> : > > > (*.mdb)};dbq=db.mdb"
> : > > >
> : > > > Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> : > > > [Microsoft][ODBC Microsoft Access Driver] Cannot open database
> : >'(unknown)'.
> : > > > It may not be a database that your application recognizes, or the
> : file
> : >may
> : > > > be corrupt.
> : > > > D:\IGF1STIMULANT\MP\../../marketplacecode/usPro/addcart.asp, line
> : 3
>
>
>
> ---
> You are currently subscribed to activeserverpages as: [EMAIL PROTECTED]
> To unsubscribe send a blank email to
%%email.unsub%%


---
You are currently subscribed to activeserverpages as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]

Reply via email to