Make Read-Only Front End

J

John

I've got an access db that's been split into a front and back end. I've
made a copy of the front end and want to make it read-only so that I and
other users can play around with it without mucking up the underlying data.

Can anyone tel me what my options are for this? I think I've read that I
need to go through setting up passwords and user permissions but is this the
only (or correct) option?

Thanks

John
 
R

Rick Brandt

John said:
I've got an access db that's been split into a front and back end. I've made
a copy of the front end and want to make it read-only so that I and other
users can play around with it without mucking up the underlying data.

Can anyone tel me what my options are for this? I think I've read that I need
to go through setting up passwords and user permissions but is this the only
(or correct) option?
Click to expand...

If you just want to avoid "accidents" add a prefix to all table names and then
create queries using the old names of the tables. The queries can be made read
only by setting their RecordSetType to "Snapshot".

If you want to avoid "mischief" then you need to apply security.
 
B

Barry-Jon

Make copies of both the Front End and the Back End. If you only copy
the Front End it will still be linked to the same Back End (which I
assume is production data). When you copy the Back End rename it and
then copy the Front End (rename it). Then you need to repoint the
copied front end to the copied back end. I have someone who wanted to
"play around" with a database I had developed. They thought they were
great and made a copy of the Front End - then proceeded to delete all
the data in the linked tables - the production data !!
 
A

Albert D. Kallal

If you are looking to protect the design, and not allow people to modify
forms etc, then just distribute a mde.

A mde is in fact a "run only" version of your software. Just go
tools->database utilities->make mde

Remember, you distribute the mde to your users..but you MUST NOT loose the
mdb that you used to make the mde, as there is NO WAY to recover the mdb
file from a mde...this is a one way street....

So, give your users a mde...and you keep the mdb FE for you...
 
J

John

Thank you all for your replies. I have to say I'm a little confused now
with the various options and warnings of data doom!

I'm really just looking to make a front end that will contain select queries
only and make it impossible to delete / change the back end data in anyway.
Also I'd rather not duplicate the back end as a) it's quite large, b) it
gets updated every month and c) I can just see someone (including myself)
deleting the wrong one by mistake!

The ideal would be a front end with a couple of select queries that points
to the correct back end. So I think in review I still favour the security
route although I take onboard your points, Joseph, about lock out. I also
need to read more about the MDE option as I would like to be able to edit
some VBA.

Anyway, any other feedback would be very welcome, but thanks to everyone for
your time.

Best regards

John
 
R

Rick Brandt

John said:
Thank you all for your replies. I have to say I'm a little confused
now with the various options and warnings of data doom!

I'm really just looking to make a front end that will contain select
queries only and make it impossible to delete / change the back end
data in anyway.
Click to expand...

That is what I suggested. For example, if you currently have a form bound
to a table named "Accounts" you could rename that table to "AccountsSource"
and then create a SELECT query that shows all of the fields from that
renamed table and name the query "Accounts". Your form will now use the
query instead of the table the difference being that a query can be made
read only very easily whereas a table cannot.
 
Top