bb.donnay-software.com

Roger,

Odd on this one. On prchoice, just very standard print options, when this particular user selects to use another printer, it just closes everything. New windows 11 on a new server. All work stations and server updated at the same time 3 weeks ago. All other users fine. No message from what we are told.

Default printer and other functions, like preview with acrobat,etc. All work fine. Just when he wants to select another printer.

IT person says he has reinstalled all the print drivers. Just wonder if you or anybody has ever run across this.


Suggested for him to delete all the other printers, then add them one by one testing selecting printers after each addition. Not sure he liked that option.

As far as I know there is no limit in alaska,etc on the printer name or length of the name, special characters..but maybe there is.(?)

***
I was thinking giving him a quick app to use
oPrinter := xbpprinter():new()
newarray := oPrinter:list()

Then list each printer one by one to see if it stops on a certain printer. Not sure if that would help or not.



Thanks

Fred
omni

when this particular user selects to use another printer, it just closes everything.

What does that mean? The printer choice dialog closes? The application quits?

Yes, out menu closes completely. I logged into that persons pc using teamviewer and minimized the size on our app, ran the prchoice on a small print job and it just closes, but there is a message in a big white window in the middle of the desktop but it disappears in 1 second. Just did that a minute ago. It appears to be a message from windows or one of the printers, no idea.
He sometimes prints to a printer, sometimes to microsoft pdf, and is changing the default printer to get around his issue.
Never seen anything like it and no idea why it would just close our app.

This is a lot more is more information than I had earlier. As a note, they are still on 1.6, not 2.0, if that matters. Rarely hear from them, 20 year small customer

Thanks

As a note, they are still on 1.6, not 2.0, if that matters

I would think that it just might matter.
Can you give them the latest runtime version to find out?