OK, After reading Greg's response and thinking a bit, I do have a (rather cumbersome) work-around. Here goes;
LV does a wonderful job of keeping tarck of all those nasty little details like what VI is really being called and are buffers allocatoed correctly, etc, etc. In your case, this is complicating yur life. You may be able to get around the issue you are facing by writting a wrapper VI that calls the DLL that has the VI you need shared. Use the wrapper VI instead of the orignal VI anyplace the original would have appeared in your code. This just might do the trick! Ben
