I have a VFP9 application that uses Inno Setup as its installer. I am facing a challenge because most of our users install the application on a network server. The issue arises because Inno Setup cannot recognize mapped drives when elevated privileges (admin rights) are required during installation. As a result, users must install the application using the UNC share name.
Unfortunately, many of our users are not technically savvy leading to a constant stream of support calls for assistance with installing the application to the correct UNC share location.
My question is: Is there a better way to handle this situation? I can't be the only one dealing with this issue in a FoxPro application using Inno Setup. I would appreciate any ideas or workarounds that others in the community might have.
Additional Note:
- After the initial installation, the Inno Setup wizard can prepopulate with the previously installed path (the correct UNC share name). However, due to changes in personnel or computers, users often do not use the same computer for updates each year.
- We have a new version released each year which must be installed in the same location each year. Making this a recurring problem.
Thanks in advance,
Vince
Unfortunately, many of our users are not technically savvy leading to a constant stream of support calls for assistance with installing the application to the correct UNC share location.
My question is: Is there a better way to handle this situation? I can't be the only one dealing with this issue in a FoxPro application using Inno Setup. I would appreciate any ideas or workarounds that others in the community might have.
Additional Note:
- After the initial installation, the Inno Setup wizard can prepopulate with the previously installed path (the correct UNC share name). However, due to changes in personnel or computers, users often do not use the same computer for updates each year.
- We have a new version released each year which must be installed in the same location each year. Making this a recurring problem.
Thanks in advance,
Vince