Problem with database connection
Problem with database connection
am 10.03.2005 20:35:04 von jack
Hi,
I got a web application which was connected to Access97 database. However,
few months back someone converted the database to Access 2000. This database
is uploaded on a monthly basis from client server production Access97
database. Now, when I am uploading the Access97 database, there is a problem
in connecting to the web application. The error is as following:
Microsoft OLE DB Provider for ODBC Drivers.error '80040e09'
[Microsoft][ODBC Microsoft Access Driver] Records cannot be read; no read
permission on 'tblPOSTApplicant'.
The connection string where the error pops up is as follows:
<%
myDSN="Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=C:\Inetpub\wwwroot\MBCC\post\Transcripts\data\postdat a.mdb"
set cnn = server.createobject("ADODB.Connection")
cnn.Open myDSN
set rstemp = server.createobject("ADODB.Recordset")
%>
I would appreciate any help in advance. Does the above connection string not
serve for both Access97 and Access2000?
Re: Problem with database connection
am 10.03.2005 21:15:35 von reb01501
Jack wrote:
> Hi,
> I got a web application which was connected to Access97 database.
> However, few months back someone converted the database to Access
> 2000. This database is uploaded on a monthly basis from client server
> production Access97 database. Now, when I am uploading the Access97
> database, there is a problem in connecting to the web application.
> The error is as following:
> Microsoft OLE DB Provider for ODBC Drivers.error '80040e09'
> [Microsoft][ODBC Microsoft Access Driver] Records cannot be read; no
> read permission on 'tblPOSTApplicant'.
After verifying that the file's read-only attribute is off, check the IUSR
account permissions for the folder containing the file - the account should
have Change permissions. Then verify that the permissions hwve been
inherited by the database file.
>
> The connection string where the error pops up is as follows:
>
> <%
> myDSN="Provider=Microsoft.Jet.OLEDB.4.0;" & _
> "Data
> Source=C:\Inetpub\wwwroot\MBCC\post\Transcripts\data\postdat a.mdb"
???? That can't be correct. You are getting an error from the "ODBC
Microsoft Access Driver", not from the "OLE DB Provider for Microsoft Jet".
Verify that the connection string you think is being used is in fact being
used.
Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
Re: Problem with database connection
am 10.03.2005 21:57:07 von jack
Thanks for your help Bob.
The database attached to the web application was a read-only one. So I
changed it. The IUSR_machinename permission is now read, write and and read
and execute. However, I did not find anything named Change Permission. I
found full control, modify and special permission.
With that I am still getting error.
The error message I quoted earlier was incorrect.The correct error message
was:
Error Type:
Microsoft JET Database Engine (0x80040E09)
Record(s) cannot be read; no read permission on 'tblPOSTApplicant'.
/mbcc/post/transcripts/CheckLogon.asp, line 65
Now, what else can go wrong here. Thanks. Regards.
"Bob Barrows [MVP]" wrote:
> Jack wrote:
> > Hi,
> > I got a web application which was connected to Access97 database.
> > However, few months back someone converted the database to Access
> > 2000. This database is uploaded on a monthly basis from client server
> > production Access97 database. Now, when I am uploading the Access97
> > database, there is a problem in connecting to the web application.
> > The error is as following:
> > Microsoft OLE DB Provider for ODBC Drivers.error '80040e09'
> > [Microsoft][ODBC Microsoft Access Driver] Records cannot be read; no
> > read permission on 'tblPOSTApplicant'.
>
> After verifying that the file's read-only attribute is off, check the IUSR
> account permissions for the folder containing the file - the account should
> have Change permissions. Then verify that the permissions hwve been
> inherited by the database file.
> >
> > The connection string where the error pops up is as follows:
> >
> > <%
> > myDSN="Provider=Microsoft.Jet.OLEDB.4.0;" & _
> > "Data
> > Source=C:\Inetpub\wwwroot\MBCC\post\Transcripts\data\postdat a.mdb"
>
> ???? That can't be correct. You are getting an error from the "ODBC
> Microsoft Access Driver", not from the "OLE DB Provider for Microsoft Jet".
> Verify that the connection string you think is being used is in fact being
> used.
>
>
> Bob Barrows
>
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.
>
>
>
Re: Problem with database connection
am 11.03.2005 00:39:08 von reb01501
Jack wrote:
> Thanks for your help Bob.
> The database attached to the web application was a read-only one. So I
> changed it. The IUSR_machinename permission is now read, write and
> and read and execute. However, I did not find anything named Change
> Permission. I found full control, modify and special permission.
>
The names of the permission levels vary depending on the OS. All that is
required is read/write (which equals Change or Modify)
> With that I am still getting error.
>
> The error message I quoted earlier was incorrect.The correct error
> message was:
> Error Type:
> Microsoft JET Database Engine (0x80040E09)
> Record(s) cannot be read; no read permission on 'tblPOSTApplicant'.
> /mbcc/post/transcripts/CheckLogon.asp, line 65
> Now, what else can go wrong here. Thanks. Regards.
Show us the code up to and including the line that raises the error (line
65).
This error sounds like the result of a workgroup-secured database. You don't
have to provide a user name and password when you open the database in
Access, do you?
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"