Splitting - Ready Only

I am new to splitting and security. I read "Splitting a access database, or
how to run ms-access in a multi-user mode" by Albert D. Kallal.

I split a database and created an MDE of the FE database (had to convert to
2002 to be able to do this). I distributed the MDE to a co-worker. I went
to their computer and opened the MDE which seemed to work fine. I was still
able to delete edit/delete data. I guess I thought splitting and creating an
MDE would prevent users from editing/deleting.

I want to prevent users from editing or deleting data. I want to give users
the ability to create their own queries, but only want them to be able to
view data. What is the best way to give users access to the data (read only)
and still utilize the benefits of a fe/be on a network?

Any assistance you can provide would be greatly appreciated.

Only give them read-only access to the folder where the back-end exists.
Yes, they'll get an annoying warning every time they go into the database,
but they won't be able to update it.

Alternatively, you could use Access User-Level Security. If you want to go
that route, check out
http://support.microsoft.com/support...ent/secfaq.asp (Warning:
Implementing Access User-Level Security is non-trivial. Make sure you've
read the document several times before trying, work on a copy of your
database, and don't skip any steps)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)



"KReese" wrote in message
...
I am new to splitting and security. I read "Splitting a access database,
or
how to run ms-access in a multi-user mode" by Albert D. Kallal.

I split a database and created an MDE of the FE database (had to convert
to
2002 to be able to do this). I distributed the MDE to a co-worker. I
went
to their computer and opened the MDE which seemed to work fine. I was
still
able to delete edit/delete data. I guess I thought splitting and creating
an
MDE would prevent users from editing/deleting.

I want to prevent users from editing or deleting data. I want to give
users
the ability to create their own queries, but only want them to be able to
view data. What is the best way to give users access to the data (read
only)
and still utilize the benefits of a fe/be on a network?

Any assistance you can provide would be greatly appreciated.

The link doesn't work?

"Douglas J. Steele" wrote:

Only give them read-only access to the folder where the back-end exists.
Yes, they'll get an annoying warning every time they go into the database,
but they won't be able to update it.

Alternatively, you could use Access User-Level Security. If you want to go
that route, check out
http://support.microsoft.com/support...ent/secfaq.asp (Warning:
Implementing Access User-Level Security is non-trivial. Make sure you've
read the document several times before trying, work on a copy of your
database, and don't skip any steps)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)



"KReese" wrote in message
...
I am new to splitting and security. I read "Splitting a access database,
or
how to run ms-access in a multi-user mode" by Albert D. Kallal.

I split a database and created an MDE of the FE database (had to convert
to
2002 to be able to do this). I distributed the MDE to a co-worker. I
went
to their computer and opened the MDE which seemed to work fine. I was
still
able to delete edit/delete data. I guess I thought splitting and creating
an
MDE would prevent users from editing/deleting.

I want to prevent users from editing or deleting data. I want to give
users
the ability to create their own queries, but only want them to be able to
view data. What is the best way to give users access to the data (read
only)
and still utilize the benefits of a fe/be on a network?

Any assistance you can provide would be greatly appreciated.

Works fine for me!

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)



"Kou Vang" wrote in message
...
The link doesn't work?

"Douglas J. Steele" wrote:

Only give them read-only access to the folder where the back-end exists.
Yes, they'll get an annoying warning every time they go into the
database,
but they won't be able to update it.

Alternatively, you could use Access User-Level Security. If you want to
go
that route, check out
http://support.microsoft.com/support...ent/secfaq.asp (Warning:
Implementing Access User-Level Security is non-trivial. Make sure you've
read the document several times before trying, work on a copy of your
database, and don't skip any steps)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)