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
bristolli
Active Participant
Hi there, My customer feedback for the necessity of 64bit version is that they use ODBC of 64bit and it fails to connnect to 32bit DB toolkit. Do we have work-around for connecting to 64bit ODBC? Thanks, Terry
AristosQueue (NI)
NI Employee (retired)

Not from NI. But this package from an alliance member may be useful for you:

https://decibel.ni.com/content/docs/DOC-10453

DigDoug
NI Employee (retired)

Got feedback from a customer today about his need for a 64-bit database connectivity toolkit. Since so many servers now run 64-bit OSes it makes communicating with 32-bit UDLs in LabVIEW problematic. A pretty barebones 64-bit database toolkit would probably satisfy the needs of most users. 

 

Have a great day,

Aaron

Aaron Douglass
Applications Engineer
National Instruments
NIExpert
Member

Agree it is about time to update the toolkit as well as to add 64 bit support

 

 
david_jenkinson
Active Participant

Please add native 64 bit support for the database connectivity toolkit.  Pretty Please.  With a cherry on top.

crossrulz
Knight of NI

david_jenkinson, If you want this to happen, then you need to give the idea a Kudos (the star to the left of the title).  NI looks at Kudo counts to quickly look at what is desired from the community.  Your random post will mean nothing.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
david_jenkinson
Active Participant

Ah yes.  Done.  But I hope please still means something 😕

NIExpert
Member

I found that the database toolkit will crash when using it to call stored procedures

 

I have implemented a native ADO NET DLL with LabVIEW wrappers that I have used successfully instead.      I have shared some snippets (as much as I can for now) of the C#  code below.

 

 public void ConnecttoDB(string DBServer, string catalog, int DBSecTimeout)
        {

            string connectionString = "Integrated Security = SSPI;Persist Security Info = False;Initial Catalog =" + catalog + ";Data Source =" + DBServer + ";Connection Timeout =" + DBSecTimeout;
            connection = new SqlConnection(connectionString);
            connection.Open();
        }

 

 

        //connect to a stored procedure SPName
        public void ConnecttoSP(string SPName)
        {

            command = new SqlCommand(SPName, connection);
            command.CommandType = CommandType.StoredProcedure;
        }

        //Add Stored procedure parameters

        public void AddParam(string ParamName, string strValue, ParameterDirection Direction)
        {
            command.Parameters.AddWithValue(ParamName, strValue).Direction = Direction; ;

        }

///repeat for other data types

 

//below are wrapped into higher level functions

 SqlDataReader reader = command.ExecuteReader();

  reader.Close();

  command.Dispose();

   connection.Close();

 

 

 

RedJohn75766
Member

I'm guessing there is no change on this issue from 2012?

AtulS
Member

Still no response from NI....Smiley Sad