I am using InstallShield Express 5.0 to install my VFP 8.0 application. I have used the same InstallShield setup.exe to install my application on several pc's with no problem. Recently, I attempted to install the application on a clients pc and the program would not install properly. When the LAN administrator logs into the pc, the installation program runs fine. In addition, the application also runs correctly. However, when the user logs into the pc and attempts to run the program, we get ole errors that say certain active x controls are not registered. We believe the problem is related to the fact that the Installshield program is installing the setup files under to account of the user. How can we instruct the Installshield application to install the application for all users of the computer?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VFP INSTALLSHIELD PROBLEM
- Thread starter WIREMESH
- Start date
bobmpalmer
Programmer
wiremarsh
This is to do with the Customer Information Dialogue Box option under Customize and setup appearence.
In our original install we did'nt check this item and like you, had problems when a user installs.
If you check out ALLUSERS in the help you will see how this property affects the install.
If you don't select this dialogue box the install defaults to per-user install!!
Bob Palmer
The most common solution is H2O!
This is to do with the Customer Information Dialogue Box option under Customize and setup appearence.
In our original install we did'nt check this item and like you, had problems when a user installs.
If you check out ALLUSERS in the help you will see how this property affects the install.
If you don't select this dialogue box the install defaults to per-user install!!
Bob Palmer
The most common solution is H2O!
A possible problem you may be encountering is that the computer with problems has a HD formatted NTFS (which allows directory rights to be enforced) and the other computers which worked fine have HD's formatted using FAT.
If this is the case, you'd have to be more careful about which directories get written to by your application (ie: don't store any data files, or any files at all that are written to, in the \Program Files\... directories)
- Bill
Get the best answers to your questions -- See FAQ481-4875.
If this is the case, you'd have to be more careful about which directories get written to by your application (ie: don't store any data files, or any files at all that are written to, in the \Program Files\... directories)
- Bill
Get the best answers to your questions -- See FAQ481-4875.
If your application is intended to allow all users to get to the same data files, then the location of those data files (DBFs/CDXs/DBC/ etc) becomes important.
Putting them in a "My Documents" subdirectory won't work, since they'll be created during Install in the Administrator's "My Documents", and when "Plain Old User" logs in he'll have absolutely No Access to the Adminstrator's documents.
Putting them in a directory off the root (eg C:\MyAppData) won't work since normal users won't have access there either. (You can force Installshield to set the access rights to such a directory so anyone can get to it by right-clicking that folder in InstallShield (under Specify Application Data...Files), then selecting "Properties", then clicking the "Permissions" button on the properties window. Leave the "Domain" empty, and enter "Everyone" in the "User" field, then check all the checkboxes (except "Take Ownership") and click OK.... This isn't recommended because it violates "Designed for Windows"/Windows Logo requirements)
The best location I've found is a custom folder under what InstallShield Express calls "CommonAppDataFolder", which translates (usually) to: "\Documents And Settings\All Users\Application Data". This is where app data files that are Not Documents should be stored. (They are Not Documents because one file <> one entire data set, and one file does not have a distinct visual/sensory representation (like a Letter, Song, Fax Document, etc). Best of all, every user can get to this folder with no problems.
- Bill
Get the best answers to your questions -- See FAQ481-4875.
Putting them in a "My Documents" subdirectory won't work, since they'll be created during Install in the Administrator's "My Documents", and when "Plain Old User" logs in he'll have absolutely No Access to the Adminstrator's documents.
Putting them in a directory off the root (eg C:\MyAppData) won't work since normal users won't have access there either. (You can force Installshield to set the access rights to such a directory so anyone can get to it by right-clicking that folder in InstallShield (under Specify Application Data...Files), then selecting "Properties", then clicking the "Permissions" button on the properties window. Leave the "Domain" empty, and enter "Everyone" in the "User" field, then check all the checkboxes (except "Take Ownership") and click OK.... This isn't recommended because it violates "Designed for Windows"/Windows Logo requirements)
The best location I've found is a custom folder under what InstallShield Express calls "CommonAppDataFolder", which translates (usually) to: "\Documents And Settings\All Users\Application Data". This is where app data files that are Not Documents should be stored. (They are Not Documents because one file <> one entire data set, and one file does not have a distinct visual/sensory representation (like a Letter, Song, Fax Document, etc). Best of all, every user can get to this folder with no problems.
- Bill
Get the best answers to your questions -- See FAQ481-4875.
- Status