How can I programmatically get the full path of all VIs in memory?

[MattI]

How can I programmatically get the full path of all VIs in memory? I can get the current VI's path using Property Node, but not the callers or callees paths. I can only get their names.

[srm@viewpointusa.com]

check out C:\Program Files\National Instruments\LabVIEW 6\vi.lib\Utility\sysinfo.llb\Get Memory Statistics.vi. this is a utility VI that I have used for some very usefull functions.
Stu

[MattI]

This is awesome!
Looking at the diagram, I am somewhat surprised that Open VI Reference works using just the VI names returned by Property Node:Application:All VIs In Memory when they are wired to the path input to Open VI Reference, but I guess it uses the (relative) built-in path info that we users can't see to look up the VI which is in memory, and then returns the full path.

[wiebe@CARYA]

You can use the VI name to refer to a vi in memory. (note that all VIs in
memory must have a unique name, thus LV can make a reference needing only
the name.)

To refer to a vi not in memory, LV needs a full path. The open VI reference
is polymorphic, it accepts strings and paths (as you already noticed).


"MattI" wrote in message
news:506500000005000000AC7D0000-1021771306000@exchange.ni.com...
> This is awesome!
> Looking at the diagram, I am somewhat surprised that Open VI Reference
> works using just the VI names returned by Property
> Node:Application:All VIs In Memory when they are wired to the path
> input to Open VI Reference, but I guess it uses the (relative)
> built-in path info that we users can't see to look up t
he VI which is
> in memory, and then returns the full path.

[boltzmann]

You can wire the Callees property string output to a for loop and then use indexing to pull each VI name out of the array. Wire each individual string element directly to an Open VI Reference then use this reference with the property VI Path to return the path of the each callee VI.

Marcus Monroe
National Instruments

[MattI]

Yep. That's what the vi in stu's reply does.