Re: Catching record before it saves?
- From: "Arvin Meyer [MVP]" <a@xxxxx>
- Date: Sat, 5 Jan 2008 07:29:06 -0500
One does not need to go to a new record to use Filter By Form.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
"Tofudisan" <TofuTheGreat@xxxxxxxxx> wrote in message
news:66e6330d-b2d8-4d3e-9b21-01a3ec84bd38@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I've got a small 3-user database. The GUI is Access 2K and the data
is in an MS SQL 2005 back-end.
Today I noticed some NULL records being created in the database by the
same user. In talking to the user I found out that she would go to a
new record and then use the built-in Access "Find" (binoculars button
on the toolbar) to look for records. So I know that what is happening
is that she's creating the new record and then the Find operation is
moving off of that record thereby saving it.
My question is how to still let them have the built-in Find utility
but keep them from creating the NULL records when they move off a
"new" record? Should I just use the Before Update event to catch the
record and effectively delete it when the recordset moves off of the
record?
.
- References:
- Catching record before it saves?
- From: Tofudisan
- Catching record before it saves?
- Prev by Date: Re: How to insert a '*' in certain controls when Enter is pressed.
- Next by Date: Re: Problem with Data Types
- Previous by thread: Re: Catching record before it saves?
- Next by thread: Re: password for command button?
- Index(es):
