File select popup error

[Mikee9265]

Hi, I've recently run into a problem on some windows installs where the fileselectpopup command seems to give some error and instead of the normal windows 10/11 UI to select a file, I get a UI similar to windows 3.1. 

Any ideas why that might happen?

[RobertoBozzolo]

Are you using FileSelectPopup or FileSelectPopupEx? There is a difference between those functions which show a different window to the user.

If you are using the latter, take into account the note on multithreading model that you can read in the function help.

Are you receiving an actual error and if so, which one?

[Mikee9265]

Hi Roberto,

Thank you for the prompt response. I am using "FileSelectPopup". As far as I can tell, I don't get an actual error. I do not see this behavior in the debug/release in the cvi labwindows environment. I only observe this in some installs on other computers, which makes it a bit tricky for me to see what is actually going on. The program nominally uses multi-treading but its not critical to the operation, so I can remove the multithread processes to see if that removes the issue. 

I have anecdotally heard that there might be an issue if there are readonly being checked in the file attributes, I can't confirm that is the case with my issue. I will check on the installs on the other computers to see if that is part of the problem.

[RobertoBozzolo]

Actually the Run-time Engine installed has some influence on this item: RTE2020 always shows the modern window regardless the command you use, while RTE2017 (and downwards) gives different windows for FileSelectPopup ("classic" style) and FileSelectPopupEx ("modern" style).

Which means that you need to check which runtime is present in all of your installs and consider that the "classic" style window may not be the symptom of a misbehavior.

[Mikee9265]

Hi Roberto,

Thank you for the help! For the run time engine, I guess that is something I can add in the drivers and components on the distribution to make sure the up to date version is installed. I already have NI Labwindows/CVI Shared Runtime 2020 f2 as part of the build. Do I need to add any of the other runtimes (e.g. Side by side or Labview runtime) to make sure the up to date RTE2020 is correct? 

[RobertoBozzolo]

Including the correct RTE in the distribution is normally enough to have all required software components installed at the user site. In the case of CVI, the system only accepts one shared runtime at a time, so installing version 2020 replaces previous instance of the RTE that may be present in the system.

Additionally, if you develop your app in CVI2020 you normally receive an error in case you try running it on a system with an older RTE (on the contrary you can safely develop in previous releases and run on top of 2020 RTE).

A different case is if you install a side-by-side runtime: in that case I suppose you could have different runtimes running on the system but I have no experience on that as I always use a shared runtime.

[AlinaaJoseph]

It is possible that the issue you are experiencing with the fileselectpopup command is caused by a compatibility issue between the command and the version of Windows you are running. Here are some steps you can take to try to resolve the issue:

1. Check for Updates: Make sure your Windows operating system is up to date by checking for any available updates or patches. Often, updates include bug fixes and compatibility improvements that may resolve the issue.

2. Check the Command Syntax: Double-check that the syntax of the fileselectpopup command is correct and that you are using it correctly. It is possible that a mistake in the command syntax could be causing the issue.

3. Check for Conflicts: Other programs or applications running on your computer could be conflicting with the fileselectpopup command. Try disabling any other programs that may be running in the background and see if the issue persists.

4. Try Running the Command as Administrator: Running the command as an administrator may help to resolve the issue. Right-click on the command prompt and select "Run as administrator" before running the fileselectpopup command.

5. Reinstall the Program: If none of the above steps work, try uninstalling and reinstalling the program that is using the fileselectpopup command. This may help to reset any settings or configurations that could be causing the issue.

If none of these steps work, you may want to contact the software developer or manufacturer's technical support team for further assistance. They may have additional troubleshooting steps or be able to provide a solution specific to the program you are experiencing issues with.