This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 39%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
My Access 365 application reads the list of available printers into a dialog box. It has worked for years until now. This is an excerpt of the code...
Any idea what could be causing this?
How would you characterize the crash?
Ignore this comment
Sequence of events:
I placed a breakpoint at the Application.Printers line preceded by an ON ERROR branch. It hung again in "running" mode without triggering an error.
I don't see anything unusual in the devices and printers list.
Did you try this loop in a new simple application too?
Hi,
Your code works without a problem in my Current Channel version 2407 build 17830.20166, 64 bit.
Servus
Karl
Access News, Forever, DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 41%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETV%3C/text%3E%3C/svg%3E)
Are you running ACCDB in Production? That is not a best practice.
That said, if you are, you may want to decompile the app. There is nothing wrong with that line of code.
Thank you both for your responses. I found the source of the problem.
I checked with IT to see if there had been any printer changes on Friday. I was told that, oh yeah, a new driver had been installed on one of the printers but apparently was not loaded properly. I removed that printer from devices and Applications.Printers successfully returned the printer collection. IT now has to notify every user of every one of my Access applications to look for and remove the offending printer.
Seems to me that Applications.Printers should have been smart enough to report the issue and continued on its way. I hope someone from Microsoft is listening.