Re: Jet.OLEDB and Access 2003
- From: "Douglas J. Steele" <NOSPAM_djsteele@xxxxxxxxxxxxxxxxx>
- Date: Sat, 3 Sep 2005 08:10:43 -0400
Do you have a primary key defined on the table? I believe it's necessary for
the scenario you're describing.
Also, what permissions does the security context under which ASP is running
(usually IUSR_<machine name>) on the folder where the MDB file exists? It
requires at least Read, Write, eXecute and Delete.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Radon" <Radon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A33CA8DD-007A-428D-AC05-D79A0851702B@xxxxxxxxxxxxxxxx
> I'm running an old ASP program that worked just fine w/ Access 2000
> (Win2K).
> Now, when I run it against an Access 2003 db (XP) I get the following:
> Cannot
> update. Database or object is read-only. Note that the program is able
> to
> read the db.
>
> My connection string is as follows: Provider=Microsoft.Jet.OLEDB.4.0;Data
> Source=C:\myLocalSite.mdb;Persist Security Info=False
>
> The program seems to break while executing the following:
> Set objRS = Server.CreateObject("ADODB.RecordSet")
> objRS.Open strSQLStatement, strConnect, adOpenStatic, adLockPessimistic,
> adCmdText
>
> Session("visits") = objRS("VisitorNumber") + 1
> objRS("VisitorNumber") = Session("visits")
> objRS.Update
> objRS.Close
>
> I'd appreciate if someone could help me out.
> Thanks!
>
.
- Follow-Ups:
- Re: Jet.OLEDB and Access 2003
- From: Radon
- Re: Jet.OLEDB and Access 2003
- References:
- Jet.OLEDB and Access 2003
- From: Radon
- Jet.OLEDB and Access 2003
- Prev by Date: Jet.OLEDB and Access 2003
- Next by Date: Re: Jet.OLEDB and Access 2003
- Previous by thread: Jet.OLEDB and Access 2003
- Next by thread: Re: Jet.OLEDB and Access 2003
- Index(es):
Relevant Pages
|