Read ".dll" files, the Macro "work flow" and the actual values of the variables when Macro is running
 

Hi Everybody,

I got a couple of questions about VBA. I tried to understand how the
macro ran in a very complicated worksheet. I need to save two
different ".dll" files in the C drive in order to run the macro. My
first question is: How can I read the ".dll" files? How can I know
when the macro uses them? Any software needed to be installed so as to
open them?

The macro is very long and split in different modules. My second
question is: How to read which modules run first? To be more
specific, how to read the "work flow" of the macro (step by step)?

Also, I would like to know whether any functions in Excel or VB editor
can allow me to read the actual values of the variables when the macro
is running (Of course, the macro is paused when I am reading the
values.).

Any suggestions or ideas are very welcome. Thank you very much in
advance!

Best regards,
S.

Read ".dll" files, the Macro "work flow" and the actual values of the variables when Macro is running
 

If you place a break in the code or use F8 to step through it you will
be able to see how the code executes step by step. Using the Locals
window you can see the values of variables at any time during the
execution. This can be opened under the View menu in the VBE.

Read ".dll" files, the Macro "work flow" and the actual values of the variables when Macro is running
 

Reply to your 1st question:
You can't read a ".dll" file. It's short for dynamic link library and
is compiled code. Somebody wrote source code to create the dll, but
that's typically proprietary. A dll includes one or more Public
"object" variables that allow access to it. A client application gains
access by declaring an "object" variable of the appropriate type.

Hth,
Merjet

Read ".dll" files, the Macro "work flow" and the actual values of the variables when Macro is running
 

Thank you very much for your help.

So how is the ".dll" file created?



On May 16, 11:30 am, merjet wrote:
Reply to your 1st question:
You can't read a ".dll" file. It's short for dynamic link library and
is compiled code. Somebody wrote source code to create the dll, but
that's typically proprietary. A dll includes one or more Public
"object" variables that allow access to it. A client application gains
access by declaring an "object" variable of the appropriate type.

Hth,
Merjet

Read ".dll" files, the Macro "work flow" and the actual values of the variables when Macro is running
 

So how is the ".dll" file created?

A DLL is created with a language compiler, such as Visual Basic, VB.NET or
C++.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting LLC
www.cpearson.com
(email on the web site)


wrote in message
ups.com...
Thank you very much for your help.

So how is the ".dll" file created?



On May 16, 11:30 am, merjet wrote:
Reply to your 1st question:
You can't read a ".dll" file. It's short for dynamic link library and
is compiled code. Somebody wrote source code to create the dll, but
that's typically proprietary. A dll includes one or more Public
"object" variables that allow access to it. A client application gains
access by declaring an "object" variable of the appropriate type.

Hth,
Merjet

Read ".dll" files, the Macro "work flow" and the actual values of the variables when Macro is running
 

So how is the ".dll" file created?

By writing the source code and compiling it. The code can be written
in VB6, VB.NET, C, C++, etc.

More info: http://en.wikipedia.org/wiki/Dynamic_link_library

Merjet