melodramatic
Board Regular
- Joined
- Apr 28, 2003
- Messages
- 180
- Office Version
- 365
- Platform
- Windows
I have created a macro user input interface, where users can input the info that will go to the project management files, and then simply press one of four command buttons, depending on what they want to do. The command buttons pull up the appropriate macro.
With a base of almost 100 users for this file, ONE person is having issues. He cannot run any of the macros using my commandbuttons, as his computer will not recognize the commandbutton names.
My command buttons:
- ButtonCreateNewMDR (brings up the "CreateNewMDR" macro) - on his machine, the button shows up as CommandButton1
- ButtonGetDocCtrlNum (brings up the "GetDocCtrlNum" macro) - on his machine, the button shows up as CommandButton2
- ButtonOpenEditMDR (brings up the "OpenEditMDR" macro) - on his machine, the button shows up as CommandButton3
- ButtonPrintMDR (brings up the "PrintMDR" macro) - on his machine, the button shows up as CommandButton4
It's weird - if he tries to go to properties, he can see the properties of the command button (albeit with a wrong name), but if he goes to read the coding for the button, it brings up the correctly named button. Since the two are different, the buttons he sees won't bring up the macros.
At one point, the macro kept bombing out on him. In my macro coding, at the end of the macro, once the project file closes, I tell the macro to go back to the user interface file, and I added that it was to go to the "Input" sheet. That's where he bombed out - his machine recognized that sheet as "Sheet1", not "Input" (which is what it's named in the file). But, when you look at the sheet on his computer, it clearly shows the tab is named "Input." I've fixed this issue by removing the line that sends us to the correct sheet. Since it's the only visible sheet, that line is not an issue - it was more habit on my part to put it there.
I've taught him to use the [Alt]+[F8] to bring up the macro, and that works fine. But, I can't figure out what the heck the problem with his Excel is. His suggestion that I re-do the file so that it reads commandbutton1, etc., is not going to happen. I have my system, I use my system.
I have double-checked that he did not copy down the user interface (macro) file - everyone has been instructed to only use a shortcut (thus assuring they'll pick up any changes I make). He has not.
We're using Excel 2010 & Windows 7 Professional. Does anyone have any idea what could be going on here?
With a base of almost 100 users for this file, ONE person is having issues. He cannot run any of the macros using my commandbuttons, as his computer will not recognize the commandbutton names.
My command buttons:
- ButtonCreateNewMDR (brings up the "CreateNewMDR" macro) - on his machine, the button shows up as CommandButton1
- ButtonGetDocCtrlNum (brings up the "GetDocCtrlNum" macro) - on his machine, the button shows up as CommandButton2
- ButtonOpenEditMDR (brings up the "OpenEditMDR" macro) - on his machine, the button shows up as CommandButton3
- ButtonPrintMDR (brings up the "PrintMDR" macro) - on his machine, the button shows up as CommandButton4
It's weird - if he tries to go to properties, he can see the properties of the command button (albeit with a wrong name), but if he goes to read the coding for the button, it brings up the correctly named button. Since the two are different, the buttons he sees won't bring up the macros.
At one point, the macro kept bombing out on him. In my macro coding, at the end of the macro, once the project file closes, I tell the macro to go back to the user interface file, and I added that it was to go to the "Input" sheet. That's where he bombed out - his machine recognized that sheet as "Sheet1", not "Input" (which is what it's named in the file). But, when you look at the sheet on his computer, it clearly shows the tab is named "Input." I've fixed this issue by removing the line that sends us to the correct sheet. Since it's the only visible sheet, that line is not an issue - it was more habit on my part to put it there.
I've taught him to use the [Alt]+[F8] to bring up the macro, and that works fine. But, I can't figure out what the heck the problem with his Excel is. His suggestion that I re-do the file so that it reads commandbutton1, etc., is not going to happen. I have my system, I use my system.
I have double-checked that he did not copy down the user interface (macro) file - everyone has been instructed to only use a shortcut (thus assuring they'll pick up any changes I make). He has not.
We're using Excel 2010 & Windows 7 Professional. Does anyone have any idea what could be going on here?