Labview.lib was not calld from a labview process

[dchabotVB]

I am working with our labview programers to create a Labview DLL that will be called from Labview and VB6. The code works fine with Labview but I keep getting Fatal Error: Labview.lib was not calld from a labview process. I have checked the versions of development software and the runtime versions that we are using and they matche 8.0.1. We have also preformed a mass compile of the DLL with no change.

Are there any other steps that we can take to solve this problem???

[andre.buurman@carya]

http://digital.ni.com/public.nsf/allkb/A4C3AEF93240280A86256931006FB66C?OpenDocument
 Just to make sure you know of this article, I hope its a new one and else we can look further.

http://www.groupsrv.com/computers/about566915.html
Another discussion regarding the same error message.


Message Edited by andre.buurman@carya on 06-04-2008 08:02 PM

[andre.buurman@carya]

http://forums.ni.com/ni/board/message?board.id=170&message.id=127655&query.id=62975#M127655
Here a discussion talking about the use of labview.lib functions in your dll.

Why is there the need to use functions of the labview.lib in your dll? If create multiple dll's for use in Delphi code and didn't need to use the labview.lib. I've also never had these kinds of error though.

[dchabotVB]

I have that Labview document printed out and sitting on my desk, I have read through it and have shared it with the Labview guys. The second link is the same vuage answers that I have found arround. This problem is showing up on both development systems, labview and vb. and short of taking out all of the code we have not been able to get rid of the error.

[andre.buurman@carya]

The best way to debug this problem is to eleminate functionality and see if the problem disappears. A good thing to have around is a proto type dll that only incorperates the functional calls without any functional code, only some code to check if the parameters are set and retrieved OK.

[Ben]

I have to agree with Andre.

I have developed dll from LV code that where called by VB. If you can narrow down what it is in the dll that gives you that message, we or NI may be of greater assistance.

Ben