Why can't my VI (called as a .dll from VB) get at the controls of another VI running in memory?

[dynamic]

I know this post was a while ago now but you seemed to have the answer I'm looking for. I am new to Labview and my aim is to have a series of vi's compiled into a dll (or multiple dlls) that I can load from an independant application. I then need another vi that can be run from teststand that can interact with those vi's (ie for automated testing). I think I am having similar problems with the independent memory spaces. It sounds like what you did would work for me but I am having difficulty understanding exactly what you did. Could you possibly provide a simpler breakdown [really dumb it down for me 🙂 ] or maybe post a small example.

thanks

Mike

[Ben]

Hi Mike,

It would probably be best for you to post a fresh Q (include a link to this Q as reference) with the specifics of what you are attempting.

They "key" is to get the target VI (the VI you wan to act on) into the memory space from which you are acting.

We accomplished this (see above) by controlling what memory space the tagret was created in. This accomplished by
1) Open the target from within the dll.
2) Including the target as part of the build used to create the dll.

I will try to watch for your posting,

Ben

[Ben]

Good you have already posted!

Your challenge is similar to mine in that you are dealing with the multiple memory space issue (I believe).

BUT,
you are further complicated with the fact that you are trying to access the target VI's from two applications at the same time.

You may be able to call the same dll from both environments.

Use my notes from above to get the target working from one of your dll calls. Then see if you can use the same dll called from TS.

Ben