Read only database problem

[Al Jans]

Hi,

I have a multi-user access 2k database, with a server based backend
and a local machine based front end. What I want is :

1) one group of users to have a full access (i.e. edit, delete, insert
etc data) into the system via the front end with no restrictions

2) one group of users to have read only access on the data via the
front end

However, I don't really want to use the inbuilt access security as I
don't want my users to be bothered with remembering yet another
password. I also need the read-only group of users to still be able to
execute code that inserts data I just don't want these inserts/changes
to be saved.

Is this just wishful thinking, or is there a simple (or complex)
solution to this situation?

Thanks in advance

Al

[Mike Storr]

Sorry, wishful thinking. Without using Access security, anything you setup
will be accessible by anyone who has access to the folder it resides in. You
can create your own profiles, and restrict access to forms and such by only
including those items in the frontend, but if anyone bypasses the startup
options of the db, evertything will be wide open (forms, reports and modules
can be protected by making it an mde).

Mike Storr
www.veraccess.com

Is this just wishful thinking, or is there a simple (or complex)
solution to this situation?

Thanks in advance

Al

[Keith Wilby]

al******@yahoo.com (Al Jans) wrote:

However, I don't really want to use the inbuilt access security as I
don't want my users to be bothered with remembering yet another
password.

You could set up user-level security without passwords, but make the
account names the same as the users' network log on IDs, then compare
CurrentUser with the network log on ID - if they don't match, quit nosave!

HTH - Keith.
www.keithwilby.org.uk

[Alan Webb]

Al Jans,
It's bending the rules a bit, but this has worked for me: A legit licensed
copy of Microsoft SQL Server Desktop Edition and a trial version of SQL
Server 7.0. The MSDE install got me a legal instance of the database engine
and the trial CD set up the Enterprise Manager tools for MSDE. There are
still throttles on the MSDE engine so I can't server a large organization
but because I mostly develop stuff for customers this doesn't matter. And
having SQL Server means I get its security model, which works really well
with Win NT 4.0 and 2K.

"Al Jans" <al******@yahoo.com> wrote in message
news:7b**************************@posting.google.c om...

Hi,

I have a multi-user access 2k database, with a server based backend
and a local machine based front end. What I want is :

1) one group of users to have a full access (i.e. edit, delete, insert
etc data) into the system via the front end with no restrictions

2) one group of users to have read only access on the data via the
front end

However, I don't really want to use the inbuilt access security as I
don't want my users to be bothered with remembering yet another
password. I also need the read-only group of users to still be able to
execute code that inserts data I just don't want these inserts/changes
to be saved.

Is this just wishful thinking, or is there a simple (or complex)
solution to this situation?

Thanks in advance

Al

[Peter De Baets]

There are many alternatives to using Access Security when it comes to
securing your database.

A shareware version of a simplified user security add-in - LASsie
(Light Application Security) for MS Access - is available for download
here:
http://www.peterssoftware.com/las.htm

With LASsie, you can specify that the network username is to be used
automatically as the LASsie username. This way, users don't have to
remember another username and password.

Also, there's the Access Project Security Manager from
databasecreations, Inc.:
http://www.databasecreations.com/prod_apsm.htm

Hope this helps,

Peter De Baets
Peter's Software - MS Access Tools for Developers
http://www.peterssoftware.com

al******@yahoo.com (Al Jans) wrote in message news:<7b**************************@posting.google. com>...

Hi,

I have a multi-user access 2k database, with a server based backend
and a local machine based front end. What I want is :

1) one group of users to have a full access (i.e. edit, delete, insert
etc data) into the system via the front end with no restrictions

2) one group of users to have read only access on the data via the
front end

However, I don't really want to use the inbuilt access security as I
don't want my users to be bothered with remembering yet another
password. I also need the read-only group of users to still be able to
execute code that inserts data I just don't want these inserts/changes
to be saved.

Is this just wishful thinking, or is there a simple (or complex)
solution to this situation?

Thanks in advance

Al

[Don]

I can only echo that LASSIE is the best choice for this problem, I had a
similar issue and it has saved hours of programming. In addition the
support from the author was exemplary