Printable View
Hi Peeps,
I have a vb6 MSI install which works great; I have had to log on the client PC as admin to do the install but when I log the standard user in it complains about msadodc.ocx is not registered yet it works fine if logged in as admin.
Would it be better to give the users profile admin rights and do the install that way. I am guessing that the registery entries have been put in a admin privilege section of the reg.
Any ideas please,
Jiggy!
What OS are you using Vista?
Hi Mate,
No its XP Pro SP2!
It is very wierd because if we do the install on the computer with admin profile everything works fine but if I log in as a standard user everything works except all the truegrids are blank - showing no data.
I think it has something to do with permissions for msadodc.ocx so I went in the reg and set full but I think there is another file used called comcat or something like that.
Cheers for your reply,
Jiggy!
Errr... Where did you install your database????
I suspect that the issues discussed in Specifying a Per-User or Per-Machine Installation may be relevant here.
You didn't say what packager you used. VSI 1.1 doesn't normally include the ALLUSERS property, so on XP you'd have a per-machine installation. Your symptoms sound like a per-user install however. What packager did you use?
In any case if this is what is going on you could install with the command line switches to set ALLUSERS=1 or null:
msiexec /i C:\someplace\somepackage.msi ALLUSERS=1
Command-Line Options
The alternative would be to open the MSI database with Orca and change ALLUSERS to 1 or delete the row from the Property table. It is worth checking the MSI with Orca anyway so you know what is going on, since this might not be your problem at all.
I just built a simple VB6 MSI with VSI 1.1 and tried it on XP SP3.
There is no ALLUSERS property in the MSI, and it installed per-user under the Admin account I ran the installer under.
I uninstalled and then reinstalled from the Admin account as I described above with ALLUSERS=1 and it installed per-machine as I'd expect.
You can do this or use Orca to add a Property table row ALLUSERS with 1 for its Value column.
The installation is suspect...
I suppose that's possible, but doing a per-user install produces very similar (if not identical) symptoms.Quote:
The installation is suspect...
I wonder what else may be going on here.