"vba run" command is not in "key-in" predefined commands list

Hi Behnam,

at first, please read and follow the best practices: Without knowing the product you use and exact version (e.g. build number, displayed when "version" key-in is used), often no exact answer can be provided.

BenS said:

I have to use command "vab run borderdialog" in key-in but vba not there for executing the command.

Based on what information you expect the key-in is "vba run..."?

BenS said:

but when I want to run it in "key-in", there is no selection text in key-in list that shows vba.

In MicroStation CE, the key-in to run vba macro is "macro vba run". See this page for the description.

With regards,

  Jan

Hi Jan,

Many thanks for your help.

When I execute "macro vba run" a dialog box opens that requests the macro name. The macro file is in the folder that MicroStation knows based on variables, also it shows the "Macros in" path which is correct but it can not show the Macro name therefore "Run" button is disable.

My macro file  is *.mvba and its job is filling project specific title block. I could run it before but after new installation of MicroStation promis.e it doesn't work like before.

What happens if you type in

MACRO VBA RUN BORDERDIALOG

Assuming that "BorderDialog" is the name of the macro you intend to run?

BenS said:

The macro file is in the folder that MicroStation knows based on variables, also it shows the "Macros in" path which is correct

Sorry, but you share so little and so fuzzy information, that it is hard to investigate the problem :-(

Why you do not share e.g. Configuration Dialog picture or content of msdebug file, so it's clear what and how configuration variables are set? Sentences like "macro file is in the folder..." tell technically nothing.

BenS said:

but it can not show the Macro name therefore "Run" button is disable.

Is macro loaded? Can be done manually in VBA Project dialog, using MS_VBAAUTOLOADPROJECTS variable or "macro vba load" key-in.

BenS said:

When I execute "macro vba run"

What key-in exactly did you run? As stated in documentation I linked, the key-in must contain (which is logical) macro module and procedure specification, so it's not only "macro vba run", but "macro vba run [project name]module name.subprocedure".

Regards,

  Jan

Solved, thanks

Solved Jan, many thanks