about create shared varibles programmatically

[brian005]

in my case, there are a lot of shared variables, i need to classify them into several levels,such as which country,which

area, which city, then shared variables, so i create country.lvlib first, then create area.lvlib under country.lvlib, after

that create city.lvlib under country.lvlib, in the end, add shared varibles under city.lvlib.
in this way, i can get variable path like this:

 \\ My Computer\country\area\city\variable1

so far, everything is ok.

then i want to add shared variables to city.lvlib programmatically

1. use invoke mothed: "library:open" to open city.lvlib, then add a varible, including dsc configuration
2. go back to my project, i find the variable under the city.lvlib
3. then enploy the country.lvlib library (only can enploy top-level library, i dont know why), appear error message:

    Download completed with errors (error code: -1967362038)
4. then i try to add variable to the city.lvlib manually, appear the same problem.

what is the problem?

thanks in advance

[Ray.R]

Here is what the error number says (well... it is actually a warning)..

Warning -1967362038 occurred at an unidentified location

This error code is undefined. No one has provided a description for this code, or you might have wired a number that is not an error code to the error code input.

So this does not help very much...  Can you post the vi's?

JLV

[brian005]

sorry for late relay

attached is the vi

[Thaison_V]

Hi Brian,

I hope you're doing well.  I did have a few background questions for you.  Are you using LabVIEW DSC 8.0 or 8.0.1?  Does setting the DSC properties (the section you have in the disable structure) affect whether this error occurs or not?  This may give us a clue if one of the properties you are selecting may be causing a warning.  Another thing is that although the error message says that the error occured at an unidentified location, you can typically use the debugging tools to either highlight the execution or step through to figure out where the error actually occurs.  It may also help to have a mock-up of your VI and Project, where you can narrow down the project and VI code to where you are still seeing the error.  Fill us in on some of these details, and we will be glad to help.  Have a great day!

Thaison V
Applications Engineer
National Instruments