database variant to data function not working

[JHebert]

I've got the same problem.  I have LV 8.5 and the Database Variant to Data will not drag onto the block diagram.  I tried replacing the dir.mnu file, as suggested in the knowledgebase article, but LV has a heart attack when I start it up.

I am not looking forward to spending half a day reinstalling LV and all my toolkits.  It doesn't look like that helps anyhow. 

How do I "repair" my installation, as suggested by Amanda?  I ran the setup program on my install CD, but there is no repair option.

Edit: Oddly, I am able to open a previous project that uses this function and copy and paste it to my new project.

Message Edited by JHebert on 01-18-2008 08:54 AM

[Amanda_H]

Hi,

You can repair software installations by navigating to your Control Panel and choosing Add or Remove Programs. Click Change/Remove next to National Instruments Software. You should then be able to navigate to your specific version of LabVIEW and select Repair.

[Nils_Gokemeijer]

It appears to me that the new installer 'Database Connectivity Toolkit 1.0.2' does not install the '_DB Variant to Data' directory, which contains all the variant vis.

Copying that folder from a previous LabVIEW (installed with 'Database Connectivity Toolkit 1.0.1 or 1.0.0) changes to problem to this:

'Database Variant to Data: Library version is incompatible with XNode Version'

How to get the right '_DB Variant to Data directory?'

[mikeporter]

If all else fails, you can use the regular Variant to Data function to recover database data. It works just as well.

Mike...

[Karunya_R]

Hi,

I also have database connectivity toolkit 1.0.2 installed on my system with LabVIEW 8.6.1. 

I was able to locate the folder _db variant to data at C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\addons\database\_DB Variant To Data.

You can also do as Mike suggested and see if that works for you. Like he said, there shouldn't be much of a difference between use the actual VI and pulling it from that particulr folder.

[Nils_Gokemeijer]

Well, looks like I got it working.

This is what I did:

-removed and reinstalled database toolkit (did not help)

-copied _DB Variant to Data folder from 8.5 into 8.6 (this caused a governor library compatibility issue)

-copied dir.mnu from NI website (this caused the loss of utils and advanced pallettes)

-copied db_util.mnu and db_adv.mnu from 8.5 (now the pallettes are back)

- replaced all the 'Database variant to data' in my software (including vis that are part of the distribution) with the one in the (new?) database pallette

I am guessing I have more than one 'database variant to data' vi in my vi.lib tree, but I don't know where and which one is the right one.

They are native, i.e. in some lvlib file, so I don't think you can browse for them.

[Karunya_R]

Hi Nils,

Thank you for posting your solution.

Like I mentioned in my previous post, you should be able to browse to the location of the _db variant to data in that folder. Ideally when you upgrade your program to the new LabVIEW version, it should automatically use the functions in the new version. You shouldn't have to replace the  Database variant to data vi in the new version.

Either way, its working now. So congrats on that!

[mindsclay]

I am experience the same issue with version 10. Yes, I can replace the variant to data vi with the "other" variant to data vi. However, there remains the question. Why did the database version of variant to data stop working? I am seeing this in conjunction with "Library version is incompatible with XNode version" and "This VI claims to be part of a library, but the library does not claim to own this VI." After re-saving a vi to the library that didn't recognize it, the vi still won't execute because of sub-vi that are broken. These sub-vi's are locked and I cannot see why that don't work except one has class conflict issues. These vi's in question worked last week. They have suddenly stopped working. I checked a second computer with LabVIEW installed and I see the same issues, yet that computer hasn't been used.

Why does the "This VI claims to be part of a library, but the library does not claim to own this VI." issue occur? This has happened several times and I think it has something to do with the variant to data vi not working.

[Scott_A]

Mindsclay,

Have you already tried repairing your version of LabVIEW?  What version of the Database Connectivity toolkit were you using?

Have you tried the following links to solve these errors?

This VI claims to be part of a library, but that library does not claim to own this VI

Library version is incompatible with XNode version

Did anything change from when these VI's were working and when they did not?