tracking development

[id]

I  am looking for a w3ay to tracak and monitor labview VI development.  Are there properties like number of wires/number of objects that I can get by writing a VI to parse directories and files to obtian this type of info?  Please chime in

[altenbach]

We have tools...debug...VI metrics (at least in LabVIEW professional).

I am sure you could write a program to iterate through a pile of files and collect the info.

[id]

I have and here it is.  The problem is that it errors out on certain files and I dont understand why it is doing that.

[RavensFan]

What do the errors say?

You should have a Close VI reference inside your For Loop.  You keep opening VI's but never close them.

You should NOT have a shift register on that error wire.  If you do get an error inside that loop, it will carry into all later iterations and you won't be able to open the VI or get its data (assuming those functions have standard error functionality which means they won't execute if there is an incoming error.)