Access Stops Working When Exit Print Preview of 1 Rerport via Esc Key

[rjgriffin46]

I have one (of several) reports in my front end which opens in Report View. The report can be placed into Print Preview, either by clicking the Windows print preview icon or clicking the Access tab and selecting print preview. When exiting Print Preview, I am in the habit of doing so by hitting the Esc key on the keyboard. This causes Access to stop working and close. It does not create a backup file. it does leave the lock file open, but you can open the front end again without any problem. Exiting by clicking the red X Close Print Preview button on the ribbon, or just "X"-ing the tab closed does so without this problem. The record source is a simple 1 table query.

None of the other reports exhibit this problem.



I have not found this problem in internet searching, though I have not yet tried the Microsoft Community.

I would appreciate hearing from anyone who has experienced this or may have some causal theories and solutions.

Thanks

[ranman256]

dont hit ESC key. press close button.

[rjgriffin46]

I've advised my users accordingly.

But to try to eliminate the error a suggestion from Microsoft Community was to de and re-compile which I've started and am encountering a lot of errors.

Any thoughts on this?

[NTC]

the decompile will necessarily flush out lines of code that are orphaned - - let's say one changed the name of a control - the code for an event linked to the old control name may still be there. So this can be harmless - and yet should be cleared out as long as one is going thru the effort to decompile.

so not everything found is necessarily an indication of other problems per se - just that a lot of changes have taken place and things were not cleaned up along the way.

it is not really related directly to your original post per se...that issue is really about the topic of users having too much design control (changing from report view to print preview) and you really should consider creating a print preview object instead to keep users from messing around with object parameters....