report won't open - even in design view

[Robgould]

Hello,

I have a problem that has me completely baffled.

There is a database that has been in place for years. Worked fine yesterday. Nobody admits to changing anything.

Today two seperate reports will not work. Both give and error saying "You've canceled the previous operation." I get this error when I try to use a command button to run the report.

The report is based on a query. The query runs fine.

When I try to open the report right from the report menu, it asks me for begining and ending dates.....the nothing. The cursor flashes for a minute and nothing happens. No errors. Nothing.

So I tried to open the report in design view. Nothing happens. The cursor changes to an hourglass for a minute, then goes away. The report will not open.

I thought it might just be corrupted somehow, so I copied and pasted the report from another version of the database. I get exactly the same result.

I am really scratching my butt at this point and would appreciate any advice you might have.

Thanks.

 

[MStCyr]

Maybe you should try the following for starters:

1) repair / compact the current database

2) create a new blank database and import all of the objects from the "bad" database into the new one.

 

[Keith Nichols]

go to back ups or recreate

Hello,
I am really scratching my butt at this point and would appreciate any advice you might have.
Thanks.

Hi Rob,

Making a big assumption that regular back ups have been made:

When things get a bit pear shaped like this, after a compact and repair then back up, I delete the problem object then import it from the previous back up.

My database is still in the final stages of development so the problems are mostly my fault and this resolves them. However, when it hasn't, I have had to go back to earlier versions to find a working copy and deduce what is going on.

Sometimes, I have found that something external to the problem object has been changed which buggers it all up. In these cases, I Have gone back to earlier versions of the database until I found one that worked and then tried to deduce the relevant difference between the two.

Having said all that, to this inexperienced Accesser, it sounds like the object is corrupt and a working copy from an earlier version will do the trick.

If you are in the unfortunate position of not having back ups, try the import into a new database, and then, if needed, recreate the object from scratch using nothing of the original.