ruined by compacting

  • Thread starter Thread starter Kevin3NF
  • Start date Start date
K

Kevin3NF

Can you open that fiel directly? Is there a shape.ldb file in the
directory? Is anyone else using the db? I'm no ASP pro, but it looks like
a local development environment.

I doubt seriously if the compact ruined the database, and yes regular
backups are always a good idea. :-)
 
I posted a question last night about why my db was so big. One suggestion
was to go to Tools, Database Utilities, then select Compact and Repair.
Now, I get an error on the ASp page which is supposed to connect to this
database:

Microsoft JET Database Engine (0x80004005)
The Microsoft Jet database engine cannot open the file
'c:\inetpub\wwwroot\grace\shape.mdb'. It is already opened exclusively by
another user, or you need permission to view its data.
/grace/shape.asp, line 8


I restarted my computer, same result. Wish I would have backed up my
database.

What the heck? I am new to Access, so anything you think is obvious is
something I'd like to hear.
 
I have checked out all the items you mentioned, even before i posted. This
was just me on my local machine; nobody else involved. I even rebooted.
 
If you're positive that you don't have a locking database file in the same folder as your
..mdb file, then you might start by following the troubleshooting tips in KB 183060--INFO:
Troubleshooting Guide for 80004005 and Other Error Messages

http://support.microsoft.com/?id=183060

Another possibility might be found in KB 174943, although the error message is not quite
the same:
http://support.microsoft.com/?id=174943

You replied "I have checked out all the items you mentioned, even before i posted." What
was the result of attempting to open this database using Access? Does it open at all?

You might try creating a brand new database, and importing all objects into it from the
suspect database.

Tom
_______________________________________


I have checked out all the items you mentioned, even before i posted. This
was just me on my local machine; nobody else involved. I even rebooted.


_______________________________________
 
Thanks.

To answer your question, I simply opened the db, no problem.

Good thing is, I still have my copy on the web, and it doesn't give me the
same error
 
Comments inline:


Kevin3NF said:
If you can open the database, then there is nothing wrong with it.....
Click to expand...

Well, why would I get that error, then?
please post the results of the troubleshooting from the links Tom provided
below.
Click to expand...

It will probably be later this afternoon or late tonight before I can get to
this. It's on my home machine and I am at work now.
 
For the benefit of those of us who don't know what the IUSR permission is, can you briefly
explain what it is or point us to a KB article?

Thanks
___________________________________


Turned out to be that when I compacted, it lost the IUSR permission.

thanks!
 
IUSR is short for Internet user, which means anyone who tries to insert,
retrieve, delete, or update info on the database. My database had given
read/write permissions to ISUR, but when I compacted it, those permissions
were lost. To fix it, I right-clicked the mdb file(this is in Windows 2000),
went to Properties, went to security, and found which users were permitted
to do things. I clicked the add button and added IUSR and IWAM.
 
Thank You! The reason I am interested, is because sometime in the not-so-distant future I
want to learn how to use a web page to access an Access database. That's something that I
have never done yet.

I think I know why this happened now. During the compact process, a new database is
created (db1.mdb?). If all goes well, the original source DB is deleted, and the new one
is renamed to the original name. The operating system is apparently not propagating the
file permissions during this process.

Merry Christmas and Happy Holidays.

Tom
_____________________________________

IUSR is short for Internet user, which means anyone who tries to insert,
retrieve, delete, or update info on the database. My database had given
read/write permissions to ISUR, but when I compacted it, those permissions
were lost. To fix it, I right-clicked the mdb file(this is in Windows 2000),
went to Properties, went to security, and found which users were permitted
to do things. I clicked the add button and added IUSR and IWAM.


_____________________________________


For the benefit of those of us who don't know what the IUSR permission is, can you briefly
explain what it is or point us to a KB article?

Thanks
___________________________________


Turned out to be that when I compacted, it lost the IUSR permission.

thanks!
 
Back
Top