First of all I can't say I heard anywhere before that files get corrupted when written to program files, also not with UAC in control. Setup is working with sufficient privileges in order to write to program files, no matter what files. The exe itself also is left untouched and not corrupted. Your dbfs just look to me like the unencrypted versions ou install, as I don't see how your encrypted data looks I can't judge that of course, but the files are written 1:1 by Installshield. The corruption cannot really occur there, as the files remain unchanged, changes are then written to Virtualstore and then also read from there. Problematic is, that each user will have it's own Virtualstore and so it's own copy of the file.
The feature of ISX is not very hidden. I alrady said you right click on the files you install. Within Installshield of course, within the ISX project.
There are, as mostly, many ways to do the same stuff. Simply open your ISX project now or start a new one. In the ISX project, at one step you define the files you want to install and at that step you can right click on the files and then define permissions, not directly in the context menu, but click through to "properties", properties is always an interesting submenu dialog, isn't it?
If you use the Project Assistant tab of ISX, you have a step "Application Files". There you see the destination computer and it's folders and put the files you want to install there on the right side, in the directory listing within [ProfgramFilesFolder] and a subfolder for your company and one for the application you put the files. As I said earlier, simply right click on the file you want to set permissions. And as already said choose "Properties" frm the context menu. Now you're in the general tab and in the bottom left corner is a button labeled "Permissions". Guess what it does.
If you use the Installation Designer tab, almost the same destination computer folders and files can be seen at step 2 (Specify Application Data) in the Files subnote.
When you're in that Permissions dialog of cause ISE can't know what users are on the destination computer, but click on Help to let ISX explain how you set permissions.
Now right click on the names, ISX adds [%USERDOMAIN], so you actually can set permissions for the domain the installation user belongs to. Also you can use genreal names like EVERYONE with or without the domain set. I'd add both to make sure. And below you set eg "Full Control".
Now you lower the security for those files, but then it's ok from the perspective, that you only do that for the files you want users to write to, eg your dbfs.
There of course is the alternative to install into application data. Just go over to the folders of the ISE project Files dialog and see there is an AppDataFolder and CommonFilesFolder. Right click on destination computer, then on "Show predefined folder" and you find more.
Are you never curious about the stuff yyou see on screen in general, right click on something, click on something, explore the possibilities? Especially if you have a problem with file permission, admittedly you first need to know you have such a problem, then it's only natural to explore the spot, where you define what files to install in your installation project.
Bye, Olaf.
You can also see this