Re: Locking in Queries for Reports
- From: "Arno R" <arracomn_o_s_p_a_m@xxxxxxxxx>
- Date: Fri, 29 Feb 2008 14:19:23 +0100
"Donald Calloway" <drcalloway@xxxxxxxxxxx> schreef in bericht news:2dSxj.43311$R_5.28324@xxxxxxxxxxx
I have written an application which includes 13 reports based on 39
individual queries. If a superuser happens to open any of these queries
and performs filtering of a dataset to satisfy a particular demand for
information outside of a report then re-saves the altered query by
accident, whenever a report on which that query is based is run the
results will not be as expected. How can a query itself be set as
read-only so that it cannot be modified by accident so this doesn't happen?
Is your app secured ??
You can't make query's read-only when the app is not secured.
==>> Teach your superusers to make and use their own query's.
A few other idea's:
Give them a few 'own' query's to use.
You could make copies of the needed query's and give these query's names like
_QrySuperUser_FilterOnWhatever and such
Or give them another frontend for analysing purposes.
Arno R
.
- References:
- Locking in Queries for Reports
- From: Donald Calloway
- Locking in Queries for Reports
- Prev by Date: Re: Is Access my man?
- Next by Date: Re: Locking in Queries for Reports
- Previous by thread: Locking in Queries for Reports
- Next by thread: Re: Locking in Queries for Reports
- Index(es):
Relevant Pages
|