"load code resource" not loading code

[shadedmj]

After fighting a long time, finally have a .lsb file.

I use "Load code resource" and don't receive an error nor acknowledgement.  Running the vi comes back with "Object code is not loaded" on that block.

If it didn't accept the code, I wish LabView would put up a message of why it couldn't.  Or even a prompt confirming the code loaded if it did load.

Note: I am using an evaluation version while LabView is being purchased.  Is this why I can't load code?

[JasonSmith]

I have encountered this problem when I have created LSB files from DLLs created in LabWindows/CVI.  I resolved the issue by changing the Target Settings to export "Include File Symbols" only.  If the Target Settings are set to export "Include File and Marked Symbols" you will experience the problem you described.

The Target Settings can be found on the Build menu of your project in LabWindows/CVI.

If you are not using LabWindows/CVI to create your DLL this will not work, but you may be able to find a similar option in your development environment.

[shadedmj]

Apologies, I should have mentioned more in the original post.  I'm using LabView V8 Evaluation (Full version), and the C++ from Microsoft Visual C++ 2005 to make the LSB.

When this was happening to you, were you also getting the "no confirmation or error" from LabView??

[JasonSmith]

I did encounter the same problem, where there was no error message but it was not actually loading my code.  I just tried creating my DLL in Visual C++ 2003 (I don't have 2005 on my machine) and everything working fine in LabVIEW.  I followed the instructions found on pages 3-15 and 3-16 of the Using External Code in LabVIEW document, which I have linked below:

Using External Code in LabVIEW

I found that I could cause my LSB to fail to load if I skipped step 10 in this document, where you specify the path to the Module Definition File.  Verify that you have made this change (and all the others in the procedure), and let us know how it works.

[shadedmj]

I probably won't be getting back to you.  My customer has changed software specs, C++ code now has to have another origin.

So....  I don't need CIN's immediately anymore, but may investigate them when my project is complete.

Thanks for the help though.