Import a macro into a .xlsx file without opening Visual Basic for Applications

[sspatriots]

Is it possible to import a macro into a .xlsx file without having to open Visual Basic for Applications? I have a macro that I wrote that multiple users will only import to use one time. The macro only changes the printer setup and printer configuration for a one time use. We don't even save the .xlsx as a .xlsm when we are done. We just close the file. I could generate an instruction on how to import the macro using Visual Basic for Applications, but I think users would get nervous as soon as that VB screen pops open. Was hoping to find a way to avoid opening it and still access the macro to change the print settings for that one time use.


Thanks, SS

 

[Logit]

Modify this example : How to run VBA Macro Daily without opening Excel file autiomtically?

 

[Dan_W]

Is it possible to import a macro into a .xlsx file without having to open Visual Basic for Applications? I have a macro that I wrote that multiple users will only import to use one time. The macro only changes the printer setup and printer configuration for a one time use. We don't even save the .xlsx as a .xlsm when we are done. We just close the file. I could generate an instruction on how to import the macro using Visual Basic for Applications, but I think users would get nervous as soon as that VB screen pops open. Was hoping to find a way to avoid opening it and still access the macro to change the print settings for that one time use.


Thanks, SS

Depending on the code you're using, you wouldn't need to use VBA at all - for tasks like the one you're using VBA for, you could just convert it into VBScript (which is a subset of VB) and run it from Windows. For what you're describing, it's pretty much what VBScript was designed for - for IT departments in companies to run things on users computers (like printer configurations, etc), but again, it depends on the actual code you've got.

 

[sspatriots]

Depending on the code you're using, you wouldn't need to use VBA at all - for tasks like the one you're using VBA for, you could just convert it into VBScript (which is a subset of VB) and run it from Windows. For what you're describing, it's pretty much what VBScript was designed for - for IT departments in companies to run things on users computers (like printer configurations, etc), but again, it depends on the actual code you've got.

Thanks. I will need to read up on VB Script and give it a shot.