One method is to give them a front-end that only has queries in it that point
to the tables in the backend using the Table IN pathname technique. You set
the query's Recordset Type property to Snapshot.
Here is a sample query using the In technique. You can save the query with
the name of the table so the user's still see the same table name.
SELECT *
FROM FAQ IN 'F:\Newsgroup Answers_2K.mdb';
Another option would be to use something like Duane Hookom's Query By Form
applet at
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='DH Query By Form'
***FEATURES***
The DH QBF is a complete query by form applet that can be easily integrated
into any existing Access application. Typically, the functionality provided by
DH QBF can replace many "canned" reports. The developer imports several forms,
tables, a query, and a report from the DH_QBF.mdb, creates some master
queries, and deploys.
The developer creates one or more master queries that join tables, alias
field names, create calculated columns, etc. The users can then select a
master query (data source) from a drop-down and then select up to 30 fields
from the master query. Users can define sorting and criteria as well as
grouping and totaling. All of this "design" information is stored in two
tables for re-use.
The results of the queries are displayed in a datasheet subform contained in a
main form. The main form has options to send/export the records to print, Word
table, Word merge, Excel, HTML, CSV, Merge to Report, or a graph. Most formats
allow the user to automatically open the target application. The Word merge
process will open a new Word document and link to the merge fields.
John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County
