Problem running VBA macro from button - vl-vbarun

[Anonymous]

Hi

Can someone please shed some light as to why one operator out of four of us, can't run vba macros from a lisp command?  I've checked the permissions and trusted folder locations etc, and can't find anything obviously wrong.

I have a number of buttons on a tool palette that has a macro line similar to "(vl-vbarun "X:/Programs/MTMERGE.dvb!MTMERGE") in it.  Whenever this particular operator clicks the button (or types in long hand at the prompt, the following happens (and nothing else).

 

It just adds that random 'T' at the end and nothing else happens, least of all any attempt to fire the macro.  I've also tried a less crude method using (vl-vbaload) first then (vl-vbarun). The vbaload part seems to work, but the vbarun part just returns 'T'.

I'm not clued up with lisp so very stumped as to what's going on here. 

Any help would be most appreciated.

Many thanks

Graham

[Alfred.NESWADBA]

Hi,

what happens when you don't use LISP to call that?

Same should work using command _-VBARUN, at least you should get messages if errors happened.

- alfred -

[Anonymous]

Hi

Thanks for the suggestion.

If not using lisp it all works ok.  I substituted the lisp code with normal command line text to load the dvb then run the macro and it works fine. Problem now is though, that the second time the script is executed it flags up a warning about the dvb file already being loaded.

This is the command string behind the button

_-vbaload "X:/Central Library/Reference Files/Programs/MTMERGE.dvb" _-vbarun "MTMERGE" 

Cheers

[Anonymous · Accepted solution]

Temporary work-around is to use lisp code for the load part and command line entry for the run part, all within the same string.

It's a very strange problem. Can't figure out why just one PC doesn't like lisp to call vbarun......

[Anonymous]

I have the same problem (Student Version 2017)

Any solution?

[Anonymous]

My temporary solution was as my post above.  However there are other issues with the PC in question where it won't run all code correctly, so that PC is going to have to be nuked and reinstalled.

[Ed__Jobe]

I prefer to avoid using vbarun all together. I define lisp command wrappers for my macros. This not only makes menu macros simpler, but makes it so that you can hit the Enter key to repeat the command. Also, auotcomplete recognizes the command, so you can just type it.

[Anonymous]

I did that years back for another company, but couldn't remember the code (not being a lisp bloke).  Can you share the necessary code please?  Also, do you know if it's possible to have that code in a file on a network drive so all PC's can read and load it when starting AutoCAD?

Cheers 🙂

[Ed__Jobe]

The code is posted at the link I gave you.

I put the code in a cui mnl file so it loads with the menu. You can have a cui on the network.

[Ed__Jobe]

The one problem with putting your vba and lisp on the network is that you can't make changes to it while its in use. I have everything local to each pc and when I update the menu/code, I copy it local. There are several ways to do this. I have a custom dll that loads on start up and checks for updates.