LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
vix

64-bit Database Toolkit

Status: Completed

Available with LabVIEW 2019 and later. 

The 64-bit version of Database Toolkit hasn't been release yet and the usage of 32-bit version with LabVIEW 64 isn't officially supported.

I think it's time to release it...

Vix
-------------------------------------------
In claris non fit interpretatio

-------------------------------------------
Using LV from 7
Using LW/CVI from 6.0
37 Comments
Yakov
Member

Dear National Instruments,

We've been your faithful customer for over a decade. We've invested millions of dollars into labview code.

All of our developer use full blown ($$$) labview licenses not a student version.

We purchase your hardware and run-time licenses to be used in systems installed around the globe.

Our application relies heavily on database connectivity. Call me old-fashioned, but I think that database connectivity is a core functionality of any platform. I don't think you can make a claim that you have a 64 bit version of labview available unless you support database connectivity.

We would like to see National Instruments not as one of "gone by night" enterprises chasing every new flashy named cool tech, but as a stable platform provider, with long term support and continuation of products offered.

 

 

 

david_jenkinson
Active Participant

I must say, this is really causing me headache.  It literally has broken an app I spent many hours on, it hasn't been used since we migrated to 64-bit labview.  It is preventing me from going down a road for a new database application using labview, that is on my plate right now.  Which is sad.  I've been using labview since 1997 and this is the first time I'm unable to accomplish what I want to do, I need to consider another option.  And I can't defend it to my manager, I have nothing to say but NI has chosen not to support it.  It doesn't bode well in the face of other valid options (c#, python etc) that are being argued for in my group.  I'd rather use labview, but I think it's an inevitability moving away given this is not the first time dropping support for things in subsequent versions has caused much re-coding/development on my end.  (See my thread elswhere on new "AVI2" methods dropping support for metadata in frames, that was fun).

This thread has been open since 2012.  Kind of nuts.

/startrant

We've got a VLM with over 20 licenses.  If I can't feel confident in updating to later disk versions, why pay for the updates?  It's not cheap, and I'm going to recommend against it actually.  I think we'll remain more stable as a lab freezing on a certain version of labview/teststand and not risk losing functionality, given the inevitability of migrating away anyway.

/endrant

Darren
Proven Zealot
Status changed to: In Development
 
EricR
Active Participant

Darren has already beat me to it but we are actively working on a solution for this. 

Eric Reffett | Director, Product Management | 1.512.683.8165 | ni.com
david_jenkinson
Active Participant

Any ETA? I would really love to see this soon. thanks

Darren
Proven Zealot

No specific ETA. We have prioritized this feature for investigation and possible implementation in an upcoming release.

david_jenkinson
Active Participant

Given that there is no ETA and is possibly only at the investigation point, if that, does NI at least have any official suggestions or recommendations for a work around, especially for those that already have coded applications that worked fine in the 32-bit world (other than going back to using 32-bit labview/teststand/vision etc)?

EricR
Active Participant

David (and everyone else watching this thread),

 

This feature is in development.  It will be available in the next release.  If you sign up for the beta, and you contact me (eric.reffett@ni.com) I'll happily get you a version of the toolkit that will work with the beta drop we do in the beta program.  While I won't post an exact schedule of software releases in a public forum like this, it is safe to assume that when one of the developers on the team changes the status to "In Development", it means we are actively working on the project and will release it in the next calendar year. 

 

Hopefully this addresses any remaining concerns related to this thread. 

Eric Reffett | Director, Product Management | 1.512.683.8165 | ni.com
Karthikyn
Member

@Eric/NI Team,

 

I well aware that there has been a lot of work going on the 64bit platform support and I heard you clearly that the official release will be in the next calendar year.  However I'm also curious at the same time to know if there is any update on the beta drop and its availability so that we can try out.  I would highly appreciate your comments on this!

 

Karthik

EricR
Active Participant

Karthik,

 

Have you signed up for the Beta program?  We will only announce schedules and software availability within that program.  That said, I can confirm what you are looking for is completed and is part of what we intend to provide as an early beta.  Again, I will not provide exact schedules in this public forum but I believe the timeline of "soon" is an accurate enough statement from any reasonable definition of the word.

 

-Eric

Eric Reffett | Director, Product Management | 1.512.683.8165 | ni.com