12-05-2012 10:59 PM
I have a data cluster that I am working to write to either Access 2007 thru 2010 and/or SQL Server Express 2008 thru 2012 all on a Windows 7 64 bit OS. Some of the elements are long strings that I put delimited data for the raw trace data. The fields can be 10's of KB long. With Access I cannot stuff any string >255char into the memo field. With SQL Server Express 2008R2 - 2012 I found that if the strings are >32767 they again fail to fill the memo fields. The Access write or reads work fine otherwise, just not the listed offending fields in the cases mentioned. Anyone else having the issue or a solution?
12-06-2012 06:26 PM
Hi Sunshine,
What is the source of your data? Would it be possible for you to break the long strings into two separate strings?
12-06-2012 06:48 PM
This is an older post, but may help you.
LAVA forums
http://lavag.org/topic/1776-access-memo-field-length/
12-06-2012 10:57 PM
I stated the data is a cluster with a long string field.I have the strings bronek up in the relational data table, but I wanted to have an overall test array accumulator for the test data field. The issue is this is a feature that by definition of the database and DB interface tools it is specified to be able to do this operation on this data. No the LAVA post is an old an useless rehash if the issue with no solid solution and was not even clear on the extent of the issue across both Microsoft Platform interfaces with Labview. I have used the basis MS ADO drivers with VB6 and been doing this for years with older versions of SQL Server and Express editions and Access. I was able to turn this into the support center and have them research it and see if it generated a CAR for solution by the NI development team. Thanks for the inputs though.
12-07-2012 05:49 AM
If the long string field has repetitive data, you might be able to compress it using GZIP to reduce it's size below the 32K limitation you mentioned.
GZIP compress/uncompress of string using .NET
12-07-2012 11:20 AM
While I can and have worked around the issue for the time being, I still should be corrected to work as specified. This is a significant deficiency of the NI driver for ADO connections to databases and severely limits it's utility.