Our Access 97 database is a single-file (non-splitted, pure Access)
hosted no a network server, accessed regularly by a handful of users
around the office.
Until recently (until the Great Blackout, actually), there have been
no problem with the database. It seems to handle simultaneous users
fine and did not cause any grief. The blackout corrupted the DB, but
we restored a pre-blackout version, so everything was good for a
while.
We did notice though, that ever since the black out, the database has
been experiencing various problems. Usually little things that
Compact / Repair would fix, but every now and then, we would have
unfixably corrupted forms / reports, and we would have to import
working versions of them from an older backup in a blank database.
Just recently, we experienced the weirdest problem yet. The users
were chugging along nicely when all of a sudden, they would boot up
the DB and be confronted with an "Compile Error: Automation Error".
The code would break in the Switchboard, on the line "Dim dbs As
Database". Several forms / reports would also not function when
opened manually from the DB window.
I did some searching on this, and found some instances where broken
references were the cause of grief, so I checked Tool --> References,
but everything seemed okay: the usual 3 libraries were checked off,
and the DLL files seem to be present and accounted for.
Now here is the great part, I try importing all the objects into a
blank database, and when I reach certain items, I get the scariest
error I've seen as a young programmer: "Automation Error: Catastrophic
Error"! A form and a report also fail to import with "Unexpected
Error (35012)". Funny enough, the swithboard imported and functions
without problems.
Does anyone know what is wrong with my database? Would splitting the
database alleviate these issues? Why does the database have problems
all of a sudden?
Thank you for taking your time and reading this monstrous post. I'm
rather rattled by this. Any comments / suggestions would be greatly
appreciated.
hosted no a network server, accessed regularly by a handful of users
around the office.
Until recently (until the Great Blackout, actually), there have been
no problem with the database. It seems to handle simultaneous users
fine and did not cause any grief. The blackout corrupted the DB, but
we restored a pre-blackout version, so everything was good for a
while.
We did notice though, that ever since the black out, the database has
been experiencing various problems. Usually little things that
Compact / Repair would fix, but every now and then, we would have
unfixably corrupted forms / reports, and we would have to import
working versions of them from an older backup in a blank database.
Just recently, we experienced the weirdest problem yet. The users
were chugging along nicely when all of a sudden, they would boot up
the DB and be confronted with an "Compile Error: Automation Error".
The code would break in the Switchboard, on the line "Dim dbs As
Database". Several forms / reports would also not function when
opened manually from the DB window.
I did some searching on this, and found some instances where broken
references were the cause of grief, so I checked Tool --> References,
but everything seemed okay: the usual 3 libraries were checked off,
and the DLL files seem to be present and accounted for.
Now here is the great part, I try importing all the objects into a
blank database, and when I reach certain items, I get the scariest
error I've seen as a young programmer: "Automation Error: Catastrophic
Error"! A form and a report also fail to import with "Unexpected
Error (35012)". Funny enough, the swithboard imported and functions
without problems.
Does anyone know what is wrong with my database? Would splitting the
database alleviate these issues? Why does the database have problems
all of a sudden?
Thank you for taking your time and reading this monstrous post. I'm
rather rattled by this. Any comments / suggestions would be greatly
appreciated.
Comment