LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error updating database entry with text longer than 255 characters

Solved!
Go to solution

I'm all for minimalism, and personally use a set of ODBC methods from System.Data to interact with my databases (the ability to execute multiple semicolon separated queries in one go is something I haven't been able to do with the ADO methods) in a lean fashion. However, it seems that many LabVIEW developers don't have very much experience with databases to begin with, and I think the toolkit gives a nice abstraction to allow working in native G. You could always replace those core VIs with a cluster setup of your own and keep the core components of the toolkit, which are actually quite nice and fairly well documented.

 

I just think that, in absence of the know-how of which ADO or .NET methods to employ, such abstractions are really helpful with just "getting things working," which at the end of the day, is really what most of us are after.

0 Kudos
Message 11 of 13
(1,046 Views)

That seems to work.  I will have to brush up on my SQL query syntax, though.

 

I wasn't able to use the VIs you have, as I am still working LV2012, but your descriptions were enough to cobble together a proof-of-concept that inserted the Gettysburg address into the field, so I think my limited size issue is closed.

0 Kudos
Message 12 of 13
(1,033 Views)
To save you a bit of time this thread has very similar drivers, and I think I updated them to 2011.

http://forums.ni.com/t5/LabVIEW/Extracting-one-column-from-Database/m-p/547276#M257531

There's also a good discussion of the topic.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
Message 13 of 13
(1,023 Views)