Posts by that1guy2390

    Re: Force Single-Sided Printing with Printout Method

    I'm really sorry guys and/or gals. It appears I am a doofus.

    I found yet another (this makes 4) place to change the double-sided option in the printer properties. I changed it to single-sided and now everything works perfectly.

    Thank you so much for your time.


    Re: Force Single-Sided Printing with Printout Method

    Ok this code is really bad as I'm self taught, but here are the 2 modules involved with the actual printing. I have also attached the workbook in case you need more context.

    I have several instances of identically structured workbooks that choose which pages (ranges) to print based on set criteria. A macro runs through the list of pages and adds all which meet the criteria to a variable named rngPrint using union. When all pages have been checked and either added or skipped, I simply use rngPrint.printout. This method has been working great until we got a new printer with a double-sided print option. Now, everything prints double-sided even though the setting is turned off in the printer menu AND the printer properties within Excel. These documents cannot be double-sided as many pages go to different places.

    Is there any way to force excel to print single-sided with the printout method?

    My current workaround is to send every page as a separate job, but that is not a good long term solution since it takes so much longer and we print hundreds of pages a day.

    Thanks in advance!

    Re: Add-in not loading everytime for some users.

    Thanks for the reply. Sorry I didn't see it sooner.
    The issue actually seems to have resolved itself. I did not change anything, but it just started working. Now every user has the add-ins without any issues reported. Ghosts in the machine I guess.

    Thanks again!

    Hey All,

    I am using Decision Models's "AddLoaderV2.xla" ( ) to distribute add-ins to multiple users at work (right now that is only 4). The AddLoader and all add-ins are stored in the same shared folder on our network. For 2 of the users, the add-ins are only loaded if the user loads excel first and then opens a workbook, rather than double-clicking on a workbook to open Excel and the workbook simultaneously, the other 2 users get the add-ins no matter how they open Excel.

    Is it a problem with the way I loaded the add-in or is it something wrong with the individual user's personal settings or something else altogether?


    Re: userform textbox, restricting special character entry

    Try pasting this into the code of the userform. Obviously, this only works for "textbox1"

    Private Sub TextBox1_KeyPress(ByVal KeyAscii As MSForms.ReturnInteger)Select Case KeyAscii
        Case Asc("0") To Asc("9")
        Case Asc("A") To Asc("Z")
        Case Asc("a") To Asc("z")
        Case Else
            KeyAscii = 0
    End Select
    End Sub

    Re: ActiveWorkbook.Names returns "=#NAME?"

    Quote from rory;773158

    IIRC whenever you use a new (i.e. post 2003) function, a hidden name is created. I assume it has something to do with backwards compatibility - possibly how they made the compatibility pack work.

    Just an update: You turned out to be 100% right. I am using the iferror() function and it is causing excel to add the named range specified earlier. I just wrote a simple if to skip over any hidden named ranges since it appears sumifs() and other new functions can cause similar errors.


    Re: ActiveWorkbook.Names returns "=#NAME?"

    Thanks for the reply.

    Here was the output for the errant range:

    _xlfn.IFERROR =#NAME? False

    I didn't think of the possibility of a hidden range, as I have never used them. I ran the following code:

    then deleted the offending range from the "Name Manager".

    Hopefully, my other code will work now that there are no errant ranges.

    Thanks, Rory!


    Hey All,

    I am trying to set up some code that loops through the named ranges in a workbook and am encountering some errors. Some digging led me to discover that the the first named range the code finds is "=#NAME?"



    ='Cut List'!$AU$1:$BF$63
    ='Cut List'!$AU$65:$BF$127
    ='Cut List'!$AF$82:$AP$107

    in the immediate window.

    The name manager window does not show any named ranges with any errors that I can see.

    If anyone has any ideas on what could be causing the errant named range, I would appreciate the help.

    Thanks, Don