LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Where is a list of error codes?

Is there an online list of error codes for various libraries?  I am noticing in CVI that sometimes only a couple error codes are listed, but I need a more extensive list.  Is this information online somewhere?
0 Kudos
Message 1 of 6
(4,189 Views)

There is not a single source for error codes: they are listed in several include files that you can find in CVI installation.

However, almost every library has a GetXXXErrorString function that can be used to obtain a descriptive explanation of the errors of this library: this is true for RS232, Analisys, NI-DAQ... In toolslib library there is also a GetGeneralErrorString function that conglobates errors from UIR library, toolbox and (if I'm not wrong) formatting library.

Now, while detecting an error you can act at least three ways: for developing purposes it is enough to show the context help for return code or error field parameters in every function panel of CVI libraries: in the help all possible errors are usually listed; or you can open the include file associated with this function panel (there is a specific button in function panel toolbar for this); for user information, you can pass the error code to those GetXXXErrorString and popup a message explaining the error.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
Message 2 of 6
(4,177 Views)
Thanks for the information.  That will be helpful in the future.  However, it wasn't able to help me with a particular problem like I'd hoped. 
 
I am trying to use some existing code for this project, where they had developed in labwindows 4.0.1.  The problem is an error -95, "Database DLL could not be loaded."  I can't find any help on what dll this could be.  I had hoped there would be more detailed information on these very general error messages.  All I can get from the header file (cvi_db.h) is that the name is DB_DLL_NOT_LOADED. 
 
I probably should have asked: Where can I get information on how to troubleshoot these errors.
0 Kudos
Message 3 of 6
(4,165 Views)

CVI_db.h is a file installed by the SQL Toolkit for CVI, a toolkit that permits to connect to various databases and execute sql instructions to read / write to them. If I'm not wrong this toolkit is now part of the more general Enterprise Connectivity Toolset.

This error is probably due to the fact that you don't have this software in your system so that some function is missing an external dll.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
Message 4 of 6
(4,161 Views)

I did install the sql toolkit as part of my cvi 7.0 install (almost immediately after), but I didn't know what compability issues I might have because the code was written for a previous version of the sql toolkit.  The error code I'm receiving isn't even defined in the newer cvi_db.h

A little more information is probably helpful now.  I installed cvi 7.0 and the new libraries that I had with it in the developer suite (including sql toolkit).  However, as I think I mentioned, this code was written years ago for cvi 4.0.  For some reason, they included cvi_db.h in the project headers and had a copy of several files (the fp, h, lib), within the project directory.  How this worked, I don't know, but I'm told it did.  Now, I'm trying to build this project (I can build and run) with having these files as part of the project, but also having installed only the newer version of the sql toolkit. 

My guess is that one part of this problem is the conflicting versions being used of sql toolkit?  However, I haven't seen a way to download the older toolkit to try.  I also can't build when I remove the old header file. 

0 Kudos
Message 5 of 6
(4,157 Views)

I apologize, I thought I'd posted this sooner. 

I found the answer to my compile problem.  The project had included an old library in its file list.  I replaced it with my newer installed sql toolkit library.

0 Kudos
Message 6 of 6
(4,110 Views)