S
Si_Blakely
I am installing Office 2003 Pro on workstations. However, the customer wants
to prevent most users from creating and modifying Access databases - but they
need to use Access databases.
We could use Access Runtime, but many users roam from workstation to
workstation, and a user could find themselves with full Access2003 installed
when they should not have, or vice versa.
Can we use policies to restrict full Access to the equivalent functionality
of the Access Runtime. The best I can see is Custom Menu Item restrictions -
but I cannot find the documentation to identify all the visible menu items to
hide.
Any ideas - thanks in advance
Simon
to prevent most users from creating and modifying Access databases - but they
need to use Access databases.
We could use Access Runtime, but many users roam from workstation to
workstation, and a user could find themselves with full Access2003 installed
when they should not have, or vice versa.
Can we use policies to restrict full Access to the equivalent functionality
of the Access Runtime. The best I can see is Custom Menu Item restrictions -
but I cannot find the documentation to identify all the visible menu items to
hide.
Any ideas - thanks in advance
Simon