MS Access Closes in print preview

[Debased]

MS Access Closes in print preview: Revisited

I tried the solution of : new db, import all objects, however, for the one form referred to below, it still causes Access to close.

Could it just be that the form has so many graphics that it can't handle the print job? I don't care whether I ever print the form or not but the fact that it causes it to close does cause concern.
Thanks

Original Thread:

I have a form with subforms. When I go to print preview and select "Page" and then change the page setting from portrait to landscape I get this message:

Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience. then is creates a back up and reopens.
I have tried compact and repair.

No other problems with this db and I don't really need this function..I was just wanting to look at the form on a hard copy, but I'm wondering if this isn't the beginning of the end you know...should I do the thing I've seen recommended about: create new db, import everything etc??????????

By the way, thanks again for all your help! It has been much appreciated on this current project, which except for this bit of hassel has been going well!!

 

[Kevin_S]

Try compacting and repairing the database...

If this does not solve the problem try creating a new database and importing all of the objecting into the new database as you may have a corrupted file...

HTH,
Kev

 

[Debased]

I am asking those interested to re-address this thread. I did not want to start a new one because I have noticed that is frowned upon however, wasn't sure how to get it started again.

I edited the original thread: please review and respond if you can.
Thanks

 

[Rich]

Forms are not designed to be printed, use a Report instead.
Having said that I have the odd one or two forms that I print, or used to, one of them behaved the same as yours, there's no code behind it, I couldn't fathom the reason for it, deleting importing etc. made no difference it flatly refused to print and would close the db, yet an almost identical one had no problem
I ended up creating a Report

 

[Debased]

Thanks Rich. I don't need to print it at all or even need a report at this point. It was just for design purposes that I wanted to print it.

Having said that, do you think it's ok to continue with this db and not worry about corruption? Or would you suggest recreating the form or any other suggestions??
thanks