securing a design query

[hertfordkc]

We have a database where the principal data is normally retrieved either by last name, account number, or lot number. Occasionally, a user has only partial information, e.g. a first name and a phone number, part of a street address....
An experienced user might construct a query in design view, plug in partial criteria, and then switch to datasheet view. This usually presents few enough candidates that the needed record can be found. The problem with this approach is that it appears to me to give the casual user edit, add, and delete capability in the underlying database.
I glanced at the split form, but it appears to me that it really isn't designed to be used in a query situation. I've also tried a form - subform, but have run into problems forcing one or the other to requery.


Any suggestions or questions might help me past this senior moment.
Thanks.

[June7]

Check out these tutorials:
http://www.datapigtechnologies.com/f...earchform.html
http://www.datapigtechnologies.com/f...tomfilter.html

[hertfordkc]

Your first tutorial gives a "close enough" solution. Thanks.