Access database encountering errors !?!

[Guest]

I'm developing a system in Access 2K. I'm having a problem. When I run my database (double click on mdb file). I get just a plain gray window. When I try to run 'compact and repair', I get 'MS ACCESS has encountered an error and will have to be restarted - an error log is being created'. I have never seen the log and have no idea where it is written to. Does anyone know the secret
This system sometimes runs and sometimes after an inocuous change this is what happens when I run it
This is a split database. How can I tell which part is causing the problem?

 

[Wayne Morgan]

Try the following links about database corruption.

http://members.iinet.net.au/~allenbrowne/ser-25.html
http://members.iinet.net.au/~allenbrowne/ser-47.html

Also, make sure you have the current Office 2000 service pack (3) and Jet
4.0 service pack (8, 7 for WinME) installed.

http://support.microsoft.com/default.aspx?kbid=239114

http://www.microsoft.com/downloads/...70-47d0-4306-9fa4-8e92d36332fe&DisplayLang=en

--
Wayne Morgan
Microsoft Access MVP

I'm developing a system in Access 2K. I'm having a problem. When I run my

database (double click on mdb file). I get just a plain gray window. When I
try to run 'compact and repair', I get 'MS ACCESS has encountered an error
and will have to be restarted - an error log is being created'. I have never
seen the log and have no idea where it is written to. Does anyone know the
secret?

This system sometimes runs and sometimes after an inocuous change this is what happens when I run it.
This is a split database. How can I tell which part is causing the

problem?

 

[Rolls]

Try importing ALL the objects into a blamk database. Then compact it. Your
existing one appears to be corrupted and unrepairable, perhaps due to never
having compacted, not being properly shut down, etc.

 

[Rolls]

The purpose of this step is to copy obects only, not the temporary tables
that are created by query operation through normal use of the database.
Temporary (hidden) objects are what causes the MDB size to expand enormously
in normal operation, between compacts. Often this corrects problems with
databases that have been uncompacted for a long time and are unrepairable.

A) This step does not destroy "table relationships" (or did you mean
referential integrity?) or database operation.

B) It does not alter the original MDB.

It's beginning to look like you may have had another problem such as deleted
or renamed objects. If that's the case you'll have to retrace all object
dependencies in the database. Or something is wrong with table
normalization or VBA code - a potentially more complicated and
time-consuming process to debug and correct.

 

[Wayne Morgan]

Importing the objects from the old database, by default, should get the
table relationships as well. In the Import Objects dialog box there is an
Options button. If you click it, you should see some additional options at
the bottom of the dialog. One of them is the option to import relationships.

Importing from within a new database should have NO effect on the old
database that you are importing from. Close the database and see if there is
a lock file (*.ldb) in the database's folder. If there is an ldb file with
the same name as the database and no one is using the mdb file, delete the
ldb file and try again. There will be an ldb file created for each mdb file
(front-end and back-end) and the mdw file (if you are using it).

--
Wayne Morgan
Microsoft Access MVP

I have Access 2000 SP3 (9.0.7616) and Jet SP8.

I followed someone else's advice and created a new .mdb and imported all

objects to it. Now I cannot open either the old or the new database. I get a
message that 'another user is trying to update the same data at the same
time'. I don't understand this so no-one can be.

I've also learned that doing the above, I have lost my table relationships

which were very very complex and will take hours to recreate.