Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
passing arguments by postion through application.run
I am trying to call a macro from a seperate workbook than the one that called
it, but the sub calling the other sub needs to pass named arguments (noh(),nohl()) but the application.run method does not allow the passing of named arguments, it says it they need to be passed by postion. I'm not quite sure what that means, how do I cause that other macro to be open "workbook1!module1.macro",noh,nohl while passing those arguments (variables) either with application.run or another syntax? |
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
passing arguments by postion through application.run
ApplicationRun "workbook1.xls!module1.macro",noh,nohl
where noh and noh1 ae the variables holding the values passed. -- Regards, Tom Ogilvy "ben" wrote in message ... I am trying to call a macro from a seperate workbook than the one that called it, but the sub calling the other sub needs to pass named arguments (noh(),nohl()) but the application.run method does not allow the passing of named arguments, it says it they need to be passed by postion. I'm not quite sure what that means, how do I cause that other macro to be open "workbook1!module1.macro",noh,nohl while passing those arguments (variables) either with application.run or another syntax? |
#3
Posted to microsoft.public.excel.programming
|
|||
|
|||
passing arguments by postion through application.run
Application.Run toexp + ".xls!module1.otay", noh, nohl
is the exact code i am using where toexp = "BagSof1" I have ran in break just to be sure the variable is assigned correctly. and it still does not call the macro, excel hovers over that statement like it's trying to load a workbook or something then skips it with 'on error resume next' but when i turn it off it gives me an error box that says only '400' with no explination and the help button does nothing "Tom Ogilvy" wrote: ApplicationRun "workbook1.xls!module1.macro",noh,nohl where noh and noh1 ae the variables holding the values passed. -- Regards, Tom Ogilvy "ben" wrote in message ... I am trying to call a macro from a seperate workbook than the one that called it, but the sub calling the other sub needs to pass named arguments (noh(),nohl()) but the application.run method does not allow the passing of named arguments, it says it they need to be passed by postion. I'm not quite sure what that means, how do I cause that other macro to be open "workbook1!module1.macro",noh,nohl while passing those arguments (variables) either with application.run or another syntax? |
#4
Posted to microsoft.public.excel.programming
|
|||
|
|||
passing arguments by postion through application.run
Is BagSof1.xls open. It should be.
Using application.Run is pretty straightforward. I use it all the time to call the functions in the Analysis Toolpak - VBA (as one example). -- Regards. Tom Ogilvy "ben" wrote in message ... Application.Run toexp + ".xls!module1.otay", noh, nohl is the exact code i am using where toexp = "BagSof1" I have ran in break just to be sure the variable is assigned correctly. and it still does not call the macro, excel hovers over that statement like it's trying to load a workbook or something then skips it with 'on error resume next' but when i turn it off it gives me an error box that says only '400' with no explination and the help button does nothing "Tom Ogilvy" wrote: ApplicationRun "workbook1.xls!module1.macro",noh,nohl where noh and noh1 ae the variables holding the values passed. -- Regards, Tom Ogilvy "ben" wrote in message ... I am trying to call a macro from a seperate workbook than the one that called it, but the sub calling the other sub needs to pass named arguments (noh(),nohl()) but the application.run method does not allow the passing of named arguments, it says it they need to be passed by postion. I'm not quite sure what that means, how do I cause that other macro to be open "workbook1!module1.macro",noh,nohl while passing those arguments (variables) either with application.run or another syntax? |
#5
Posted to microsoft.public.excel.programming
|
|||
|
|||
passing arguments by postion through application.run
yes it is open, which is why i thought it very strange that vba would
hesitate over that line of code, would it make a difference if i made that code public sub otay instead of just sub otay? "Tom Ogilvy" wrote: Is BagSof1.xls open. It should be. Using application.Run is pretty straightforward. I use it all the time to call the functions in the Analysis Toolpak - VBA (as one example). -- Regards. Tom Ogilvy "ben" wrote in message ... Application.Run toexp + ".xls!module1.otay", noh, nohl is the exact code i am using where toexp = "BagSof1" I have ran in break just to be sure the variable is assigned correctly. and it still does not call the macro, excel hovers over that statement like it's trying to load a workbook or something then skips it with 'on error resume next' but when i turn it off it gives me an error box that says only '400' with no explination and the help button does nothing "Tom Ogilvy" wrote: ApplicationRun "workbook1.xls!module1.macro",noh,nohl where noh and noh1 ae the variables holding the values passed. -- Regards, Tom Ogilvy "ben" wrote in message ... I am trying to call a macro from a seperate workbook than the one that called it, but the sub calling the other sub needs to pass named arguments (noh(),nohl()) but the application.run method does not allow the passing of named arguments, it says it they need to be passed by postion. I'm not quite sure what that means, how do I cause that other macro to be open "workbook1!module1.macro",noh,nohl while passing those arguments (variables) either with application.run or another syntax? |
#6
Posted to microsoft.public.excel.programming
|
|||
|
|||
passing arguments by postion through application.run
It should be public by default. It should be in a general module and NOT be
in any sheet moduler or the ThisWorkbook module. -- Regards, Tom Ogilvy "ben" wrote in message ... yes it is open, which is why i thought it very strange that vba would hesitate over that line of code, would it make a difference if i made that code public sub otay instead of just sub otay? "Tom Ogilvy" wrote: Is BagSof1.xls open. It should be. Using application.Run is pretty straightforward. I use it all the time to call the functions in the Analysis Toolpak - VBA (as one example). -- Regards. Tom Ogilvy "ben" wrote in message ... Application.Run toexp + ".xls!module1.otay", noh, nohl is the exact code i am using where toexp = "BagSof1" I have ran in break just to be sure the variable is assigned correctly. and it still does not call the macro, excel hovers over that statement like it's trying to load a workbook or something then skips it with 'on error resume next' but when i turn it off it gives me an error box that says only '400' with no explination and the help button does nothing "Tom Ogilvy" wrote: ApplicationRun "workbook1.xls!module1.macro",noh,nohl where noh and noh1 ae the variables holding the values passed. -- Regards, Tom Ogilvy "ben" wrote in message ... I am trying to call a macro from a seperate workbook than the one that called it, but the sub calling the other sub needs to pass named arguments (noh(),nohl()) but the application.run method does not allow the passing of named arguments, it says it they need to be passed by postion. I'm not quite sure what that means, how do I cause that other macro to be open "workbook1!module1.macro",noh,nohl while passing those arguments (variables) either with application.run or another syntax? |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
Passing Arguments in Excell | Excel Worksheet Functions | |||
Passing Variable Number of Arguments to a Sub | Excel Discussion (Misc queries) | |||
passing reference arguments to VBA function | Excel Programming | |||
Passing Arguments | Excel Programming | |||
Passing arguments to a sub routine... | Excel Programming |