Going from LabVIEW 2016 to 8.5 stop classes vi from operating.

[saldenisov]

I developing LabVIEW controlled experiment using version 2016. Unfortunately, I will need to transfer it to LabVIEW 8.5. When saving project to version 8.5 I'm loosing ability to work with my classes.

I made a simple test which you can see on the Figure below:

I do not understand which library I'm missing. What could be the solution to this problem?

[GerdW]

Hi saldenisov,

you're talking about a VI conversion from 2016 to 8.5!

You know there are >8 years between both LabVIEW versions?

You know there are several compiler changes in between?

General advise: Do the coding stuff in LabVIEW 8.5 when you need LV8.5 sources. Upconversion to LV2016 is much safer than backconversion…

Your 7z file contains several VIs. Apparently the "Read Numeric 2"/"Write Numeric 2" are runnable after I included them in your class…

[saldenisov]

They are runnable because they were done in 8.5 LabVIEW. So your advice is to work in 8.5, what I really do not want to do...but:(

[Yamaeda]

Were classes introduced in LV8.5?

[GerdW]

Hi Yamaeda,

OOP/classes were introduced in LV8.2…

[Yamaeda]

---

@GerdW wrote:

Hi Yamaeda,

OOP/classes were introduced in LV8.2…

---

I didn't think it was that old, seems people started using it ~2013. 🙂

/Y

[saldenisov · Accepted solution]

I found a solution:

I continued to work with LabVIEW 2016.

I've simply dublicated classes I needed in 8.5 and 2016 by simply coding them twice.

When I downgrade to 8.5 version I use classes developped in version 8.5, when I go back to 2016 I start to use version of classes developped in 2016.

Stupid, but it works:)