05-31-2018 10:13 AM
Any suggest is welcome.
I use Labview 2015 on Windows 10 and compiled an exe file for a non-Labview Windows 7 computer. It's has been working fine for years until I recently upgraded to Windows 10. The same exe file can be launched and run without showing any error message. But in areas where we used to type in numeric data cannot be loaded suddenly. The run time engine file we use is
LVRTE2015_f3Patchstd.
I tried a few things, 1. uninstall & reinstall the same engine, 2. repair, 3. uninstall and install 64-bit version engine, 4. install Window 10 SDK, 5. Enable ActiveX server when build exe, 6. Build a Installer instead of exe file, 7. Check NI USI in additional installers. Non of them works so far.
Any idea? Highly appreciative!
Solved! Go to Solution.
05-31-2018 10:17 AM
Were you running Windows7 in x32 mode and Windows10 in x64 mode? In order for the executable to be able to run, both the environment and the LabVIEW need to stay in the mode as how it was compiled.
05-31-2018 10:19 AM
Both on 64 bit.
05-31-2018 10:22 AM
My first guess is that your control is an ActiveX control (or perhaps a .NET control) that is now missing in your Windows 10 environment.
Can you tell us more about that table element we see in your screenshot? Is it really a LabVIEW native control?
Regards, Jens
05-31-2018 10:24 AM
@Minions wrote:
Were you running Windows7 in x32 mode and Windows10 in x64 mode? In order for the executable to be able to run, both the environment and the LabVIEW need to stay in the mode as how it was compiled.
Not exactly... If you built the executable with 32-bit LabVIEW, you should be able to run it on 32- or 64-bit versions of Windows, if the 32-bit run-time files are installed. If you built the executable with 64-bit LabVIEW, it will only run on 64-bit versions of Windows, if the 64-bit run-time is installed.
05-31-2018 10:25 AM
@wshao wrote:
Both on 64 bit.
Did you use 32- or 64-bit LabVIEW? If you used 64-bit, you need to install the 64-bit run-time files, not the 32-bit version you mentioned.
05-31-2018 02:53 PM
Since the runtime compatibility has been already discussed - the .NET control you are using might not exist on your Win10 machine. Possibly because you are using .NET 3.5 Framework on Windows 7 (installed by default by the OS) and this version does not get installed by default in Windows 10. You can manually add it through the Windows Features tool in your Win10 machine.
05-31-2018 03:16 PM
Thanks everyone.
Thanks to NI, found the solution.
The spreadsheet control is not an intrinsic Labview control, which is using OWC11 (Office Web Components) on Office 2003. Now with the newer version Office 2010, this add-in has to be manually installed to make the control work properly. Downloaded and installed the 2003 version OWC, problem solved.
05-31-2018 03:43 PM
@wshao wrote:
Thanks everyone.
Thanks to NI, found the solution.
The spreadsheet control is not an intrinsic Labview control, which is using OWC11 (Office Web Components) on Office 2003. Now with the newer version Office 2010, this add-in has to be manually installed to make the control work properly. Downloaded and installed the 2003 version OWC, problem solved.
Don't forget to mark your post as the solution so others may benefit from your experience! 🙂