Jenn-
You should use bound forms - and put code in the BeforeUpdate event to validate fields before they're saved no matter what the user does - close the form, move to the next, etc. You can also issue a MsgBox in BeforeUpdate to prompt the user to confirm the save. Doing in SQL behind an unbound form is doing it the hard way.
Also, when you reply on the web, be SURE to click Show Message History so that folks like me using email can see the entire thread.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On Feb 19, 2016, at 3:11 PM, jennylou68@verizon.net [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:
Hello John,
I am executing an INSERT INTO statement. I am using unbound forms to force users to consciously decide to add their submission to the database (by clicking a "Save" button). I spent to much time cleaning up records that were not complete because a user realized they were not ready and just closed out the database, leaving the partial information.
I know unbound forms are less than popular with database designers but I haven't learned any other way to do this. I have no formal training in Access so I am constantly trying to learn how to do things. My next quest will be to understand how to use bound forms more effectively.
Have a fantastic day!
Jenn
__._,_.___
Posted by: John Viescas <johnv@msn.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar