At my Wits End with a Database which won't update in ASP. Please help

[Roger Stenson]

Hi
I have an web application using Access 2000 format databases which I
developed in Windows 2000 for an Asp System. The product works fine on IIS
in the development machie and was fairly widely used as a demonstration
system with limited db's in a trial ISP who was using NT4.

The web product is supported by an inhouse utility used to build the
database for real. The database is now ready and the client wishes to go
live.

When we run the proven asp code on IIS in an XP Pro machine with the new
databases, where they were built , it immediatly halts with a messege from
the Jet Microsoft JET Database Engine "(0x80040E09) Cannot update. Database
or object is read-only." We get the the same message when we upload the
system and data to the new chosen ISP who also uses NT4.

I have spent a lot of time pouring over ACCESS security texts and have three
versions of the database, one unsecured, one secured with all the updated
functions open and one imported from the working Windows 2k environment. All
three work fine in the Windows 2k environmenet and none works on the XP
machine or with the new ISP. So the problem presumably does not relate to
Access security, an investigaion which has consumed quite a while.

As the script specifically opens the Adoconnection in read write mode and
has long been working we can't believe it is the Asp code that is the
problem.

I have recently spent some time comporaing the IIS setups in W2k and XPPro
machines but can not find any differneces which look material to me.. I
would be really grateful for some ideas on how to move this problem forward
as I am at my wits end.

Roger Stenson

 

[Douglas J. Steele]

A common problem is forgetting to grant RWXD (Read, Write, eXecute and
Delete) permission for the folder in which the MDB file exists to the ID
under which ASP executes (typically IUSR_machinename)

 

[Roger Stenson]

Thank you very much. Your proposal plus checking the Windows permissions and
sharing seem to have done the trick
I have a supplementary question. I have built a WorkGroup Admin file in the
same folder as the databases and it contains the permissions you recommend
for all the machines I put the database on.
Am I correct in assuming the Work Group database is mainly instrumental in
supporting the administrator and is not used at run time.
Otherwise I don't think I understand why the solution has worked because
when I upload the database to IIS on the Internet Host the absolute address
for for the mdw stored in the database is not aligned with the directory
used by my application in this environment.
If my hypotheses is correct I don't need to post a copy of the mdw file to
the web hose

Roger Stenson