lvanlys.dll loads from diff LV folder paths

[PoolMaster]

LabVIEW 2001.SP1, Windows7/64, FPGA Module, custom FPGA VIs and bitfile created.

How do I stop the cross loading message?  I suspect one of the FPGA functions is loading first and establishing a VI Search path I do not want.

Program loads lvanlys.dll from two location in LabVIEW folder path.  They are actually located (first & second in the image) in:

C:\Program Files (x86)\National Instruments\LabVIEW 2011\

    vi.lib\LabVIEW Targets\FPGA\RIO\R Series\78XXR\783XR\Calibration\78XXR Calibration DLL\data\lvanlys.dll

    resource\lvanlys.dll

When the project VIs load, I keep getting a warning about expected versus actual loaded paths for the lvanlys.dll file for standard <vi.lib> analysis VIs. 

Complicating matters are VIs in the project containing direct DLL calls to lvanlys.dll (reasoning unknown for inherited code) and show the path as lvanlys.* but when viewing DLL nodes of random LV analysis VIs (mean, lin fit, etc) they all show their paths as the one in the resource path shown above.

I know this problem is related to 'the first dll instance to load' behavior since opening a vi.lib analysis VI BEFORE loading the project causes the same problem BUT for the other functions (the ones originally OK).

Any advice on how to resolve this?

Thanks, Dave

[mikeporter]

My first step would be to fix the direct calls to the analysis library. I can think of a couple reasons why someone might do that in old code, but none of the reasons are valid now. For instance, there is a build option that tells LV to not remove unused routines from libraries. There was a bug in the early OOP stuff that you had to include all members of a library -- and the analysis library is VERY large.

Mike...