i cant make a ref to the global, because that would hard code the path in the static VI ref. The global may be in different locations on different systems. that is why i need to pull the path on the fly.
this only works if the global is in that vi. the point is to use the global by reference. using it by ref, it will not show up on a callee list.
The problem with pulling by reference, is that you need the path to pull it. So i need a way to get the path.
Our main program houses the global in different locations for development software and released executable software. For all of our development testing, the global is in an llb. when the software is released for use the global will be compiled into an exe that resides in a completely different location. The exe runs a secondary piece of software, stored in a different location. This secondary software is where i need to call the global by reference. Since the secondary is not inside the exe. if i strip path i will only be left with the location of the secondary software, not the exe that contains the global.
I cant run a list of callers from the secondary, trying to get the exe, because the exe calls everything by callback.
Im sorry the whole situation is very convoluted. It’s always a pain trying to conform around old issues, as opposed to cost of rewriting old code to do things right.