mihalj
Mechanical
- Apr 15, 2009
- 40
Hi,
I just got a strange problem. I made one macro that works perfectly well when I run it from SW VSTA (programming code window). When I copy /bin folder (only bin folder with all data in it) into new folder on network and run it from there using "Run" command (and pointing to .dll) my macro does not work so well anymore (at some point I even get message "Cannot open nameOfFile.dll"). I tried then to copy my complete working folder (with .vbproj and all other stuff) on network and run it from there again using .dll file and again it didn't work properly. Only way it does it is when I run it from programming code. Does anyone know am I missing something here?
I would like to be able to put my program on network and that one to be run by button (that will point to .dll) or to run it by clicking on the green pointer from Macro toolbar and call same one (bottom goal is to avoid using an open programming code whenever need to run this macro - potential delete of data).
I just got a strange problem. I made one macro that works perfectly well when I run it from SW VSTA (programming code window). When I copy /bin folder (only bin folder with all data in it) into new folder on network and run it from there using "Run" command (and pointing to .dll) my macro does not work so well anymore (at some point I even get message "Cannot open nameOfFile.dll"). I tried then to copy my complete working folder (with .vbproj and all other stuff) on network and run it from there again using .dll file and again it didn't work properly. Only way it does it is when I run it from programming code. Does anyone know am I missing something here?
I would like to be able to put my program on network and that one to be run by button (that will point to .dll) or to run it by clicking on the green pointer from Macro toolbar and call same one (bottom goal is to avoid using an open programming code whenever need to run this macro - potential delete of data).