Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/01/2017 in all areas

  1. Even without oop NI sometimes changes the internal type information. Data from 2010 to 2014 should (probably) be unflattened fine, but 2014 to 2010 may not work at all. This KB is what I've used to handle 2014->2013 communication. http://digital.ni.com/public.nsf/allkb/45E2D7BE36CE3E8B86257CCF0074D89B I dont know how this works with oop. However with objects I almost always add a 'flatten' and 'unflatten' for the object which generates a custom format string and never deal with the automatic stuff.
    2 points
  2. This does work, I have used it many times. Anecdotally, the main issue I have run into when flattening classes to string is getting the versions correct on both sides. If you have changed the class in one app but not another, you can get a 1403 error in certain cases (LabVIEW: Attempted to read flattened data of a LabVIEW class. The data is corrupt. LabVIEW could not interpret the data as any valid flattened LabVIEW class.). Some additional reading on the subject: LAVA Thread NI KB
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.