securing gatabase

[reportyemi]

I have followed the forum but it seems access 2007 security is different to
previous. I need two issue resolved
1. how can i prevent the databse i guilt from being copied?

I want users to log in ,
I have already split the database. I intend to load the front end onto about
6 computers and have an intranet of sorts. so all the computerswill be
connected to one another and to the one with the backend, They will have
patients record so i do want some decent security but not over the top. We
will use this abroad in africa

About 40 users will have ability to input data.

VERY IMPT- I want to be the only one who can change tables, querries,results
and forms. Everyone else eneters data

thanks for advice

 

[Keith Wilby]

I have followed the forum but it seems access 2007 security is different to
previous. I need two issue resolved
1. how can i prevent the databse i guilt from being copied?

I want users to log in ,
I have already split the database. I intend to load the front end onto
about
6 computers and have an intranet of sorts. so all the computerswill be
connected to one another and to the one with the backend, They will have
patients record so i do want some decent security but not over the top. We
will use this abroad in africa

About 40 users will have ability to input data.

VERY IMPT- I want to be the only one who can change tables,
querries,results
and forms. Everyone else eneters data

thanks for advice

Built-in security is supported in the "mdb" file format only in A2007, so if
that's what you're working with then follow the link to the security FAQ on
my web site. If you're using the new A2007 file format then security is not
supported.

Keith.
www.keithwilby.co.uk

 

[Scott McDaniel]

I have followed the forum but it seems access 2007 security is different to
previous. I need two issue resolved
1. how can i prevent the databse i guilt from being copied?

You can't prevent it from being copied, if this is a standard Access
database. You can make it difficult by hiding the directory, renaming
the file, etc etc but in order for your users to actually run the
database you must provide them Modify permissions on the folder
hosting that database, and if they have that level of perms they can
copy the database to a USB drive, a CD etc.

I want users to log in ,
I have already split the database. I intend to load the front end onto about
6 computers and have an intranet of sorts. so all the computerswill be
connected to one another and to the one with the backend, They will have
patients record so i do want some decent security but not over the top. We
will use this abroad in africa

About 40 users will have ability to input data.

VERY IMPT- I want to be the only one who can change tables, querries,results
and forms. Everyone else eneters data

In addition to Keith's advice, you can move your data store to a
different database engine, like SQL Server Express (which is free).
It's simple to setup and interface with Access, and you can implement
data security on the SQL Server.

You can deploy your application in the .mde format, which removes the
users ability to change Forms, Report and Modules. They can still
change Queries and Tables, however - this is where SSE would come into
play.

Scott McDaniel
Microsoft Access MVP 2009
www.infotrakker.com

 

[jmarkron via AccessMonster.com]

I have another possible scenario using 2007 and linking on table in XP/2003
format activating 2007 retro-support of WORKGROUP controls. I have posted
this information in the SETUP/CONFIGURATION forum for a thread called:
Access 2007 - Workgroup Problem. It might help you out.
........Ron

I have followed the forum but it seems access 2007 security is different to
previous. I need two issue resolved
1. how can i prevent the databse i guilt from being copied?

You can't prevent it from being copied, if this is a standard Access
database. You can make it difficult by hiding the directory, renaming
the file, etc etc but in order for your users to actually run the
database you must provide them Modify permissions on the folder
hosting that database, and if they have that level of perms they can
copy the database to a USB drive, a CD etc.

I want users to log in ,
I have already split the database. I intend to load the front end onto about

[quoted text clipped - 7 lines]

VERY IMPT- I want to be the only one who can change tables, querries,results
and forms. Everyone else eneters data

In addition to Keith's advice, you can move your data store to a
different database engine, like SQL Server Express (which is free).
It's simple to setup and interface with Access, and you can implement
data security on the SQL Server.

You can deploy your application in the .mde format, which removes the
users ability to change Forms, Report and Modules. They can still
change Queries and Tables, however - this is where SSE would come into
play.

Scott McDaniel
Microsoft Access MVP 2009
www.infotrakker.com

 

[Chris O'C via AccessMonster.com]

Nice try, but it won't help him out. Any user with a keyboard can bypass
your 2007 "retro security". All they have to do is press the shift key when
opening the accdb without your shortcut and they're in. (Or they can use a
different mdw of their own making.) Rename or delete the autoexec macro, and
next time they don't even have to use the shift key.

Chris