Normally the convention is to use an integer return code with a return code of zero meaning no error. You can then create an error cluster based on this return value. The best thing to do is to have a "Error Code Check" subVI that you plop down each time. The error cluster for the
Call Library Function function will tell you of problems with the LabVIEW <--> DLL interface. In fact, earlier versions of LabVIEW did not have an error in/error out cluser for that function. I'm not aware of being able to automatically set the error out cluster for the
Call Library Function function. With the .NET interface it's different. If the method throws an exception you get the error out cluster with the error code of 1172 I think.