crelf

I was actually looking at those when our SSP brick turned up I'd love it if it could actually read the CDs and I could lock a stach of them away in the server room so everyone could access them over the network...

That doesn't surpise me since they're dynamic - that's sort of the point The only way I can think of is to search for the text of the VI's name and hope that it comes up in an array/constant/path somewhere before the dynamic call...

Do you mean if an application is running as an executable or is an executable running?

Read this and then this, then don't come out of your room until you've had a think about what you've done.

Nope - I can only convert back to 8.0. Either way, I'd like to see a little more of what you've tried - then maybe we can help out with suggestions.

You can put the images in a picture ring: Download File:post-181-1158880116.vi Download File:post-181-1158880140.ctl

I know of a great book you should read...

I knew all that extra money we pay was worth something

Yeah - that's the first thing I do: take a marker to the spine...

The Jerk

Ewwwwwwwwwwwww! I remember those! What version of LabVIEW are you using? What version of DAQ (not DAQmx, cause it won't support the ancient evil DAQCard-1200) are you using? Also, to filter out a HH'er: please post an example of what you've already tried so we can try to help you...

Why wouldn't you want your application to start when running in executable mode? If you don't want something to happen until the user clicks a button (sounds like what you're after) the most appropriate method would be to include event handling in your application...

The datatype of the listbox should give you a clue - it's an integer, and all you need to do is pipe in a number to select the row to be highlighted: Download File:post-181-1158750468.vi

Crikey! That's some trip!

The Simpson Desert?!? Sounds like you need a drink! Although I agree with you in principle, I can't stress one thing enough: up-front design. You really need to spend some time (ie: money) at the start (especially since it's a multi-component system) and that'll save you a bunch later on. Whilst you might not be concerned about making a system perfect, with a decent amount of fore-thought, all the components should fall into place with a little thinking about the glue to interface them together. (I haven't been out to the Simpson in years - where were you?)

That's hillarious! It's like the last time I came across the Canada->US border - the immigration guy asked me what my profession was and I replied that I was an engineer - he asked what type of trains I drove...

I agree, although a functional global is different to a LV2-style global in that it traditionally doesn't just hold data, but also can perform some sort of encapsulated function on it as well.

:thumbup: That's a pretty neat implementation - have you considered creating a variant version so each of the "memory" spaces can have different structures? Also, have you considered using a string-based reference (so you can name a memory space if you want to, or just have an automatically generated name if not) rather than an integer-based reference to allow subsequent calls to reference a memoery space by name?

Whilst coercion may not always be important, knowing about cercion is always important!

It's a primitave, so I don't think there's anyway to change the default behaviour (unless there's some funky ini file setting somewhere?)

Wow - I've never heard of that scenario before! Seriously though - glad to hear LAVA helps

Welcome! I'm sure you'll get a lot from LAVA (I know I do ) - we look forward to your input!

Most people think along those lines, yet with all of our little niches and catalysts we maintain an exothermic existance

No worries - anytime!