Problem retrieving printer information

[NISMOJim]

I have been using this database error free for years. As of yesterday, when I try to open a report, I get an error message saying "There was a problem retrieving printer information for this object. The object may have been sent to a printer that is unavailable". It doesn't matter if I try to open the report from the command button or from the objects list, even in design view. Also, it's happening to all of the reports.
In searching Google, the only responses that make any sense to me talk about resetting the default printer. I don't see anything in the database about setting a default printer for any report. How can this be done in Access 2016? This report isn't even coded to print at all, just to open on the screen.
Any help will be appreciated.

[pbaldy]

Do you have a default printer set in Windows? Access uses that driver to render the report in Preview mode.

[NISMOJim]

I do have a default set, the same printer it has been for years. I reset the default to a different printer, had the same results, then back to the original printer, still no fix. I can print from other files outside of the database, so I know the printer still works from my computer.

[pbaldy]

I assume that report isn't set to go to a specific printer rather than the default? That would be set up in Page Setup on the Page tab. If that's set to default, I'm stumped.

[NISMOJim]

It is set to default. I just uninstalled & reinstalled the printer too, and reassigned it as the default printer. I test printed a page from an Excel file and it worked fine. Still getting the same error when opening a report from Access though.

[NISMOJim]

I just finished a Compact & Repair, no fix. Tried another Access database, and it all displays & prints fine.

[NISMOJim]

I tried the report again, and it is working fine again. It worked good once last night too, before erroring out again, so we'll see how long this lasts. I hope something in this thread can help someone else.

[Gicu]

Can you try to import all your objects in a brand new database file?

Cheers,