Prevent Users creating MDB files

[Adam Hall]

I have read this article on how to prevent users from being able to create
new databases.

http://support.microsoft.com/?kbid=210329

However it relates to Acces 2000. We are running Access 2003.

Does anyone know if this works for Access 2003. And does anyone have any
better ideas? i was hoping for a more robust solution like a Group Policy
setting.

Thanks

 

[TC]

I only scanned the reference briefly, but since it uses normal Access
user-level security, it should work ok for any current version of
Access.

AFAIK, Acess & Jet do not use group policies, so you won't have any
luck there.

HTH,
TC

 

[Chris Mills]

Of course, supplying custom menu's/toolbars doesn't give the user the option
to create them in the first place?

(much nicer, if possible, that they don't have an option in the first place,
than that they have an option and it's designed to fail?)

Chris

 

[Adam Hall]

I agree. I took a look at the Group Policies, and it is possible to remove
the menu options for File/New and File/Save kind of menu options, which can
be applied to general users, then allow specified users and admins access to
these menu options.

Thanks for the reply

Regards

 

[Chris Mills]

I admit, I haven't tried to load different menu's/toolbars for different
groups (hint: groups better than individual users if possible).

On a typical application, or so I imagine, it's unlikely to want ANYONE to
create new db's. So disable it for all in the application. If you have some
particular reason to create a db, I think I'd create it specifically in code
or something.

I read that you just wanted to disable creating mdb's, presumably from some
app you wrote and not necessarily from full Access. My apps just open up and
close down (so far as I know, equally <g>)

If you are looking to incorporate inherent group or security policies, I'd
have to bow out. I have never heard of a reason to need it, for the title
posted. You just remove the WDT (menus etc) for the whole app, from everywhere
a user can do it, don't you?

Menus and Toolbars can be customised through View, Toolbars. At least for
Forms and Reports, the menu and toolbar to be used is set through the Other
properties of the form or report. To make sure the user only sees your forms
or reports, you disable the database window in particular. Runtime Access does
that anyway, or you can do it in initialisation code or settings
(allowbypasskeys springs to mind)

Chris

 

[Rick Brandt]

I have read this article on how to prevent users from being able to
create new databases.

http://support.microsoft.com/?kbid=210329

However it relates to Acces 2000. We are running Access 2003.

Does anyone know if this works for Access 2003. And does anyone have
any better ideas? i was hoping for a more robust solution like a
Group Policy setting.

Thanks

Just curious...Why do you care if a user creates new databases? If there is
a legitimate business need for this then remove Access from their computers
and give them the Runtime. The Runtime has no ability to create new files
automatically.

 

[Joan Wild]

I agree. I took a look at the Group Policies, and it is possible to remove
the menu options for File/New and File/Save kind of menu options, which can
be applied to general users, then allow specified users and admins access
to these menu options.

You might be interested in viewing this Technet Webcast:
Managing Access Applications Inside an IT Organization
http://msevents.microsoft.com/CUI/W...&EventCategory=5&culture=en-US&CountryCode=US

It included information on controlling Access via Group Policies. There was
also sample code/information included for download.

 

[Adam Hall]

The reason is that users are using Access to create 'applications' that they
then expect the IT support team to manage, when no process has been followed
and no documentation has been created.

Also, they use Access as a data manipulation tool and we are trying to get
them to submit their requests to the SQL reporting services team.

I had not thought of removing the Access application and providing the
runtime instead ... not a bad idea.

 

[Rick Brandt]

The reason is that users are using Access to create 'applications'
that they then expect the IT support team to manage, when no process
has been followed and no documentation has been created.

That is a management problem. The way we deal with that at our company is
we DON'T support them. We will help them with specific data access problems
if they make the request through appropriate channels.

Also, they use Access as a data manipulation tool and we are trying
to get them to submit their requests to the SQL reporting services
team.

Adequate security settings on the SQL Server would nip that.

It's better to keep all of the Tom Cats out of your house then it is to let
them all in and then try run around neutering them.

 

[TC]

Do you have any other references for the group policies aspect?

TIA,
TC

 

[TC]

I can't see how removing File : New will help you at all. If I was a
user who wanted a new database, I'd just copy an existing one, open it
with Access, delete all the old objects, & start again with what I
wanted.

TC

 

[Joan Wild]

Do you have any other references for the group policies aspect?

No I don't. It was a recent webcast that I attended, so it was fresh in my
memory. I would bet that you'd find more information searching at the
technet site (or MSDN) or if you have specific questions ask in either
m.p.windows.group_policy or m.p.win2000.group_policy.

 

[TC]

Ok, thanks.

The perils of "AFAIK" !

TC

 

[TC]

Ok, thanks.

The perils of "AFAIK" !

TC