Seasoned Reports suddenly quit working

I have an Access97 database that is used solely for a series of
monthend reports. It is quite old, probably dates back to 1999 and
has worked flawlessly through last month and has not been touched
since then. The database resides on a network drive and has for a
year or so. Today I executed the macro that runs the reports and the
first report cannot be found. A report by that name is under the
reports tab, but when I try to open it nothing happens. When I try to
edit it, there is a quick background action and nothing else. Found
this on several reports and forms, but queries all work OK as do many
of the reports. Rebooted; relinked tables -- same thing. Backup file
worked OK. When I opened the backup and the problem databases side by
side, I noticed whenever I clicked into the window of the problem
database, there would be the same quick background action I noticed
before. Opened a new blank database and tried to import all objects
from the problem database and when the "corrupt" objects were touched
an "Automation Error" message was displayed and they were not
imported. Operationally this is not a problem since there is a
functional backup, but I don't understand what is going on here. Any
ideas?

I think this is commonly known as database corruption. Some bytes got
written in a wrong order. Access writes to disk uncontrollably and not
always correctly - this is about the only thing I dislike about it.
This is why they insist - always make backups.

Pavel

GSpiggle wrote:[color=blue]
>
> I have an Access97 database that is used solely for a series of
> monthend reports. It is quite old, probably dates back to 1999 and
> has worked flawlessly through last month and has not been touched
> since then. The database resides on a network drive and has for a
> year or so. Today I executed the macro that runs the reports and the
> first report cannot be found. A report by that name is under the
> reports tab, but when I try to open it nothing happens. When I try to
> edit it, there is a quick background action and nothing else. Found
> this on several reports and forms, but queries all work OK as do many
> of the reports. Rebooted; relinked tables -- same thing. Backup file
> worked OK. When I opened the backup and the problem databases side by
> side, I noticed whenever I clicked into the window of the problem
> database, there would be the same quick background action I noticed
> before. Opened a new blank database and tried to import all objects
> from the problem database and when the "corrupt" objects were touched
> an "Automation Error" message was displayed and they were not
> imported. Operationally this is not a problem since there is a
> functional backup, but I don't understand what is going on here. Any
> ideas?[/color]