Compact and repair problems

[Guest]

I am working for a company that has an Access database (2003). It is very
large and the person in charge compacts and repairs it every morning. I am
converting it to MS SQL Server 2000 so that they don't have these problems
any more.

Any way, this morning when he tried to run the compact and repair utility he
got an error that states "Microsoft Access has encountered a problem and
needs to close". That is it.

Then Access continues to try to run the utility. A copy of the database is
created called "db1". When it is opened another error is displayed, "Could
not create; no modify design permission for table or query
'MSysAccessObjects'."

How can I fix this?

Thanks,
enak

 

[Granny Spitz via AccessMonster.com]

Any way, this morning when he tried to run the compact and repair utility he
got an error that states "Microsoft Access has encountered a problem and
needs to close". That is it.

Make a copy of the file and work only with the copy. Keep the original
intact in case you need to send it to a recovery company. Press the shift
key down while opening the copy so the startup code doesn't execute. Open a
module and compile the code if it's not compiled. Create a new database and
import all objects from this copy into the new database. Try compacting the
new database.

 

[Guest]

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

IMHO compacting and repairing a database every morning is just crazy. If
this is just to keep the size down, it's like rebuilding the engine on your
car each morning. Eventually something will break from just doing the repair.
If it's corrupt every moring something BIG is WRONG and converting to SQL
Server might not fix the problem. Hopefully you have a recent backup.

 

[Guest]

Thanks for the replys. They know that repairing the database everyday is not
good but that is where I come in. They are about to go live with the SQL
database.

A couple of things i need to mention here:

They can still use the database and I can open it. I can not import into a
new database, however.

the database is 2000 not 2003 like I originally stated. Any other clues???

 

[Granny Spitz via AccessMonster.com]

They can still use the database and I can open it. I can not import into a
new database, however.

Why not? Not enough disk space or are you getting errors? Post the error
messages please.

the database is 2000 not 2003 like I originally stated.

That's ok. Same capacity and mostly the same functionality.

Any other clues???

Did you try compacting with JetComp? That will compact without opening the
file.

 

[Guest]

I posted the error message in my first post. It really does not say anything.
I tried JetComp.exe and it failed as soon as I executed it.

 

[Guest]

how big is big?

is it the table that is causing all the size? or do other objects contribute
significantly to size....if so you can work with a copy of the db and delete
all these other objects and strip it down to the table only...possibly this
helps.

your import error message is coming from your sql database?

 

[Granny Spitz via AccessMonster.com]

I posted the error message in my first post.

Ooooh. Usually if the users can open the database the objects can be
imported into a new database. Make sure when you import the "Show system
objects" option isn't checked so that the system tables don't get imported.

I tried JetComp.exe and it failed as soon as I executed it.

I hope you have a backup. This one has seen better days.