By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,968 Members | 1,620 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,968 IT Pros & Developers. It's quick & easy.

Read Only Front End (Access 2000/2002)

P: 3
I want to create a front end, where the linked tables are read only. The object of the exercise is to allow some users to write their own queries and reports, but prevent them from updating anything either by typing into the tables, or writing update queries.

I did this in 1999, but I can't remember what I did.

I know I could use the Access security setup, but that is not an option. The users are scattered all over the far boonies of MA and have no computer experts available on site. If they screw up the security somehow, they won't be able to use the main system.

I have found one way to do it, but it is ugly, so I'm hoping for an elegant solution.

Thanks.
Oct 28 '06 #1
Share this Question
Share on Google+
9 Replies


MMcCarthy
Expert Mod 10K+
P: 14,534
If you make your front end an mde. Keep a backup copy of the mdb development

First...
Lock all the forms to read only.
In the form properties set locked to yes

Set your startup options to hide database window and unclick all the boxes. create a customised menu bar with only those options the users will need and set this as the menu bar in startup as well.

This means the only access the users will have is through the forms and locking them makes them read only.
Oct 28 '06 #2

P: 3
What you suggest is they way the main system works.
In this front end they would be writting their own queries and reports. So an MDE won't work in this case.

Thanks
Oct 28 '06 #3

PEB
Expert 100+
P: 1,418
PEB
I'm afraid mcarthy but how the users will write their own queries? And creating Query but shouldn't be update query or append query??? Maybe invent a new query builder without those options???

It's better to search for something common to the attached tables...

The only thing that isn't convinient is that the users have permissions to create and modify queries and reports... Those are a big permissions... I don't give such a permissions to my users...

Using form filters and filters created by me - ok but creating queries...

This isn't for each head! ;)

If you organize the things that your users can't modify and create queries... it should be very ddifferent...

Your tables will be seen by queries with read only permissions... You will defend the access to the query builder and everthing will be ok...

:)


If you make your front end an mde. Keep a backup copy of the mdb development

First...
Lock all the forms to read only.
In the form properties set locked to yes

Set your startup options to hide database window and unclick all the boxes. create a customised menu bar with only those options the users will need and set this as the menu bar in startup as well.

This means the only access the users will have is through the forms and locking them makes them read only.
Oct 28 '06 #4

pks00
Expert 100+
P: 280
I want to create a front end, where the linked tables are read only. The object of the exercise is to allow some users to write their own queries and reports, but prevent them from updating anything either by typing into the tables, or writing update queries.

I did this in 1999, but I can't remember what I did.

I know I could use the Access security setup, but that is not an option. The users are scattered all over the far boonies of MA and have no computer experts available on site. If they screw up the security somehow, they won't be able to use the main system.

I have found one way to do it, but it is ugly, so I'm hoping for an elegant solution.

Thanks.

Have u considered making the backend readonly? If the network folder or the database itself is readonly, would that not then make your linked tables readonly?
Oct 29 '06 #5

P: 3
Hi:
I can't make the back end read only because it is used by the main system. That system is strictly form based and allows as little freedom as possible, You can't open it with shift, you can only use my custom menu bar, etc.

But some of them want to do their own queries and reports. If is was up to me, I wouldn't let them do even this/. But I have to protect the back end from accidental screw ups.

I can do what I want in a very simple way, but it is ugly and I know there is a better way.

I can create a form for each table. The form is set to lock all records. Open the forms hidden.
Then no query that changes the records will work.
But I know I had a much more elegant method years ago.

Another possibility is to copy the main back end in the autoexec. I backends are in the 5 meg range. The world be an opening delay, but perhaps that is the simplest answer unless I can remember what I did.
Thanks
Oct 29 '06 #6

NeoPa
Expert Mod 15k+
P: 31,347
This is only a guess really, but did you have an ODBC link before which could be set up as Read Only?
We use one of those to our back-end system.

Your system could, of course continue to use the current method but those 'others' (users - damn!) could use the R/O link.
Oct 29 '06 #7

PEB
Expert 100+
P: 1,418
PEB
It's not necessary to be a form...

A query based on a table it's a good way also...

But the query is read only...

and they can do all possible filters on the respective query...

Of course with form Autofilter...


What more???

If they want a specific join... you do it and the rest is teir homework... They can save the filters as query I think but haven't verified if the users without write rights can access this option..

:)
Oct 29 '06 #8

pks00
Expert 100+
P: 280
Have u considered looking at getting a report writer like Crystal Reports?
Oct 30 '06 #9

pks00
Expert 100+
P: 280
Here's a thought

What if u created Replica's of the database? You will need to enable Synchronisation but then ensure its only from Master to Replica

If you do this, then it doesnt matter what they do to the data as they are not touching the backend. And if they want the latest data, they have to ensure they perform the sync! By the way, u can perform that via code

here is a good link talking about replication and synchronisation from ms
http://msdn.microsoft.com/library/de...l/dbrepjet.asp

e.g. code for syncing

Public Sub SendChangeToReplica()

'Sends data or structural changes to the replica.
CurrentDb.Synchronize "C:\master.mdb", dbRepImportChanges

End Sub
Oct 30 '06 #10

Post your reply

Sign in to post your reply or Sign up for a free account.