Excel won't print more than one copy

The problem is actually a bit different. It seems that Mac Excel locks in the number of printed copies that you print on the very fist time you print a new Excel workbook. If you print 12 copies the first time, then you are stuck with 12 copies EVERY time thereafter. And this behavior travels with each Excel file to other Macs. If you have another Excel sheet and you only print one copy the first time, then that file is stuck with one copy going forward.

Microsoft apparently thought it would be a nice "feature" to remember how many copies you printed each Excel file the last time but they didn't intend to lock it in permanently. But they did years ago and still don't recognize that there is a problem. And the moderators keep spewing out that it is a printer driver problem and not a Microsoft error. As long as the Moderators don't recognize it as a problem, there is, alas, no hope.

As a possible workaround, try this...

In the Print dialog open the Presets list, select Last Used Settings then open it again & select Default Settings.. See if the number of copies returns to 1 which then can be adjusted.

The Community moderators are not microsoft employees, they are either volunteer users or contractual agents. As such they they have no control over the design & development of the software. Their function is to respond to messages posted in the Community & provide assistance at the user level as well as monitor/manage the use of the Community..

If you believe you have a valid suggestion or request use the Feedback option provided in the Help menu of the program. Feedback submitted in that way goes directly to the development team for evaluation & consideration. Include a link to this thread if you wish. You will not receive a personal reply unless more information, sample files, etc. are required.

Been there, done that but it doesn't work. Sorry.

I've used the MS Feedback many times for this problem going back at least 3-4 years. It obviously hasn't done any good. It really bothers me as a retired printing expert for a major international company. If this had happed in Windows while I was still employed, our CIO would have been on the phone to Steve Balmer and it would be fixed in days--not years.