LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Issue in moving 32 bit Labview project from 64 bit machine to 32 bit machine

Hi ,

 

I am trying the copy Labview(32 bit) source code from 64 bit machine(windows 😎 to 32 bit machine(windows).

When i opened the project in new 32 bit machine few of the vi.lib files are not recognized and they are all listed in the dependency list. Can anyone let me know what could be the issue.

For example , the below is not recognized by the project.

C:\Program Files (x86)\National Instruments\LabVIEW 2017\vi.lib\addons\database

 

Attached is the reference.

 

Regards,

Anand

 

 

 

 

0 Kudos
Message 1 of 9
(2,450 Views)

Hi Anand,

 

seems you are missing several toolkits on your new computer, like ReportGeneration and Database…

 

You need to install them with LabVIEW.

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 9
(2,443 Views)

HI GerdW,

 

The database and Report generation tools kits are already installed. But it is not recognizing it.

 

Regards,

Anand

0 Kudos
Message 3 of 9
(2,440 Views)

Hi Anand,

 

are the missing VIs located in the expected place?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 9
(2,419 Views)

Hi GerdW,

 

Complete .lvlib file is there in the expected place.

 

C:\Program Files\National Instruments\LabVIEW 2017\vi.lib\addons\database\NI_Database_API.lvlib

 

Regards,

Anand

0 Kudos
Message 5 of 9
(2,414 Views)

Hi Anand,

 

the lvlib file is just a XML description: are the VIs also in place?

 

Your project is expecting them in a certain location: are those locations the very same as expected?

 

Well, even a "Beep.vi" is missing: are you using a default LabVIEW installation at all?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 9
(2,411 Views)

Hi GerdW,

 

I am using default LabVIEW installation path only and also to remodify the subject.

 

The issue not only when opening in 32 bit machine , but occurs when we open the same project in another 64 bit machine also.

 

And also when i opening the project ,it always shows "One or more dependencies of have changed since the project was last saved " and  "Resolve Load conflict". Do you have any idea to resolve this issue. Some of the vi are always shows to old project path. Is it some where the project path hardcoded for the VIs.

 

Regards,

Anand

 

 

0 Kudos
Message 7 of 9
(2,404 Views)

Hi Anand,

 

And also when i opening the project ,it always shows "One or more dependencies of have changed since the project was last saved "

May happen when you move from one computer to a different one, don't worry…

 

and  "Resolve Load conflict". Do you have any idea to resolve this issue.

Right-click the item and "resolve conflicts"…

 

but occurs when we open the same project in another 64 bit machine also.

The toolkits might not be available for LV-64bit…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 8 of 9
(2,397 Views)

Could it be something to do with the fact that a 32 bit machine will have LV 32-bit installed into "Program Files" while on  64-bit machine it will be installed into "Program Files (x86)?

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 9 of 9
(2,389 Views)