saving custom queries in a split database

R

rwk

scenario:

- about 10 users on a network
- database split into back end (on network drive) and front ends (on C:
drives)
- some of the more knowledgeable users want to create their own custom
queries and reports, and save them for future use

If they simply save them in the front end MDBs, they will lose their
custom queries the next time an upgrade is done.

So ... do I create a 3rd MDB that gets stored locally in which they
create these custom queries, or is there a more elegant solution?

thanks


Richard
 
D

dbahooker

screw MDB use Access Data Projects and let the end users write sprocs
and views in one place instead of 200 different copies of the same
object
 
A

Albert D.Kallal

Your "other" mdb to store the queries is a good idea.

(and, likely, you probably are planning to start using mde's for the front
end anyway).

On the other hand, for most applications, such as a sales report, if you
provide the top 3-5 requests for parameters, then likely you will cover 99%
of your users. I got some complex reservation systems in soma-ccess, and I
find that after about 1, or 2 years of users working with the application,t
he requests for new repots stops, because I have supplied all that they
need.

Take a look at the following screens for report prompts, by proving users
with prompts for the top 3-5 fields, then they generally can get what they
want in the reports (and, I use the sql "where" clause of the reports for
these "prompt" forms, and thus I don't every have to modify the queries
anyway).

the example screen shots are here:
http://www.members.shaw.ca/AlbertKallal/ridesrpt/ridesrpt.html

I mean, if you got a sales database, then only a few prompts such as
location, salesrep etc should be need to cover how that data can be reported
on...
 
Top