By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,476 Members | 1,390 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,476 IT Pros & Developers. It's quick & easy.

Access 2003 Add-In Rights?

P: n/a
Greetings,

I'm having problems with the use of an Access 2003 Add-In on Windows
XP Pro. Administrative-level users have no problems running the
Add-In, but those users with restricted rights on the same computer
can't use the Add-In.

We are cloning a setup to copy to multiple identical machines, and I
just want to install the Add-In to be available to All Users without
fiddling with rights and manually installing for each person (and
making entries in their profile).

I've installed my Add-In for "All Users" on the WinXP Pro Office 2003
clone by doing the following:

1. The Add-In .mda file is copied to the folder
"C:\Documents and Settings\All Users\Application
Data\Microsoft\AddIns"

2. I run a registry file (.reg) that creates the Access v. 11.0
entries pointing to the file in the folder in (1) and telling it how
to start--the typical Add-In registry keys. I have lots of experience
with this--and simply create the entries that a manual installation
would do, but instead pointing to the All Users location for the .mda
file.

3. The security on the All Users profile Add-In folder/files (in (1)
above) is set for Everyone to have Full rights--so that the Add-In can
be modified during use--as is necessary.

4. Access 'Macro Security' is set to Low so the code can run unimpeded
(I don't know if this is truly necessary but eliminates one possible
source of my problem).

This same approach has been used in recent months for new machines
with Access 2002 (XP) with Win XP Pro, and regardless of whether they
are administrators or restricted-rights-users on those machines, the
Add-In runs without any problems. So I know the approach works. This
problem only occurs on the new Access 2003 machines.

Here's the situation for three scenarios on identical machines:

* Users who have full administrative rights to their machines have no
problems, i.e., the Add-In works as intended from the All Users
profile AddIn folder as installed above, so I know there are no code
problems or registry setting problems with the .mda file.

* Users who *had* rights when the add-in was installed manually to
their own profile have no problems, either, even when their
administrative rights were later removed. These users retain full
rights to their own profiles, so they are similar in many ways to
administrative users.

* Users with restricted rights who are loading the add-in as I
intended, through the All Users profile, can bring it up from the
add-in menu, but that's it. They cannot write to the Add-In file in
the All Users profile so are unable to use the Add-In (using it
changes data within the .mda file).

The most telling symptom: When the Add-In is selected its splash
screen pops up, but the user can't check the box that says not to show
the splash screen again. Checking/unchecking the box simply toggles a
Boolean field in a one-record administrative table that is the data
source for the splash form within the add-in. So the user can't write
even though they have Full rights to the AddIn folder/files.
---------------

I'm stumped. Your help would be greatly appreciated.

Thanks in advance, Access gurus.

-=Steve
www.CleanDataSystems.com
Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.