Setup Permissions problem???

Hi Peeps,

I have copied my VB6 app and all the folders on to the local C drive as an admin user. I have run an install using VSI 1.1 which worked fine. My problem is when I log on to the same computer as a user with limited and power user permissions when the system tries to open the database it says its read only. I have tried to change the folder permissions but it says I don't have access rights. I have logged in as admin and unticked the read only box for all subfolders and files but it still says the same. Any ideas please this is driving me mad!

Regards,

Jiggy!

Do you mean an Access database?

If so, see this article for the permissions needed.

Yes Mate!

Without know where you installed what it would be difficult to say.

BTW: Why would you copy your app and then install it on the same computer.

OK; my main problem is that I install the application on a client PC but the App, data, and reports all sit on a server. This particular customer is using some software called 'script logic' and my install seems to only install certain controls for the current users profile. If you log in as someone else you get errors. So I tried to do it on a standalone PC. What I really want is to get my install to ask for current user or all users.

Any ideas mate?

Cheers

Jiggy!

Don't think that will help for you will still need admin right to register components...

When the install is first done the current user has admin rights, which works fine. I then copy the EXE, Data, and reports to a server and it uses an INI on the local PC which I config to point to these locations. This works else where fine but for some reason on this site 'possibly script logic' if a normal user logs in and tries to use it they get errors. For instance; its seems to be MSADODC which has been registered to the installed user and MSMASK32.

???

Systems Files aren't registered to a user. They are registered to the OS so that all users can use them.

You say the user gets errors... What are the errors?

Hi Mate,

Can I start again; if we try to install as a normal user profile it fails because they do not have admin rights. So we logged in as admin and did the install and it works fine for the admin profile. If we then go in as a normal user and try to run it we get 'MSADODC.OCX or one of its dependencies not correctly registered; a file is missing or invalid'. So if we give that user admin rights and run the install which works fine and then give them normal permissions it works great. We have found that it is putting MSADODC.OCX and MSMASK32.OCX into the installers HKEY_CURRENT_USER registry and not for all users.

The problem is that 30 profiles need this on 3 machines and it can grow. Why is it putting these control entries as the local user?

Thanks mate for any help,

Jiggy!

That isn't what an installer is supposed to do unless directed to do so. Why not have the installer enter those entries into the location you want them in, since you already know what they are? or create a .reg file that you can run to put them there.

Hi Mate,

I don't know why this is doing this but it is killing me. I don't know much about Visual Studio Installer; can you give me any more details.

Thank you,

Jiggy!

New light on the situation. I have tested the install here and the OCX files in question are registered in the ROOT. Very strange!!!!!!

That's not good... You need to fix that.

Fix what? Installation in the ROOT? Do you know anything about script logic; they have that installed.

Yes, Installation in the root... Needs to be fixed.

Now I am really confused because the Visual Studio Installer deals with all of this and I don't know where the controls should be registered.

Well, evidently if it registered them in the wrong place... one of you are in error ;)