Here is an excerpt from some poor soul in India that's having the same difficulty I am, however he was never given a solution. My situation is that I have a Win2k server at work that use during the day and a WinXP Pro machine I use at home in the evening. I package my asp website up on a usb drive and take it home every night and continue working on it there (same drive letters/paths etc...). However I can't add to or change anything via ASP on my home system. I can change the .mdb file via Access but not ASP. I get the message referenced below when I try to add/update at home on the XP machine. Has anyone else seen this?

:excerpt
I have checked with the property of the mdb file. It is not set to read only. Also. To see if ADO has some problem i worked with three versions of the file. I hav worked with the files office 97, office 2000 and office 2002 versions. But all gives the same error.
"Error Type:
Microsoft JET Database Engine (0x80040E09)
Cannot update. Database or object is read-only.
/addnew.asp, line 17"
in my code line 17 is "rs.addnew " where rs is the recordset object

I think your recordset might be a read only recordset. Could you post the code where you open the recordset?

what I'm most interested in seeing is something that starts with:

rs.open

I'm curious as to the cursor and locktype you have on it.

I used recordsets for a while. I don't use them the same way anymore.

I used to use the addnew method to add new records, etc. Now, I use a read only recordset (fast and efficient), and getrows on the recordset to load it into a 2 dim array. then dump the rs and close the connection. Loop through the array to get out what you need to display. To add or update, I use sql statements (usually insert, update or delete)

Since abandoning a recordset centric approach, everything is faster and easier.

Hope this helps..

I don't think that the problem are your recordset.
I think that the anonymous user that IIS is using on your home computer. You should check that he has the right to read and write on the database.

Stéphane Lajoie

hurkle, you are correct. I had to set NTFS permissions to the folder where the db resides for the Internet User.