If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
Close form without Updating
Oh well... i've removed the validation from the table, and it still wants to
save before closing the form. Why can't it just discard what's been put on the form? It shouldn't even matter if it's valid data or Martian. I'm confused! "Klatuu" wrote: This is exactly why I never use field or table level validation. You have very little control over it. I do all my validation in the form, either at the control or the form level. That way, I have control over whether it does it, how it does it, and when it does it. The only advantage to table/field validation, is that it is always consistent throughout the application. "Swifty" wrote: |
#12
|
|||
|
|||
Close form without Updating
That is what Me.Undo does. Here is a copy/paste directly from VBA Help on
the Undo Method: If the Undo method is applied to a form, all changes to the current record are lost. If the Undo method is applied to a control, only the control itself is affected. There must be something else going on we are not seeing. "Swifty" wrote: Oh well... i've removed the validation from the table, and it still wants to save before closing the form. Why can't it just discard what's been put on the form? It shouldn't even matter if it's valid data or Martian. I'm confused! "Klatuu" wrote: This is exactly why I never use field or table level validation. You have very little control over it. I do all my validation in the form, either at the control or the form level. That way, I have control over whether it does it, how it does it, and when it does it. The only advantage to table/field validation, is that it is always consistent throughout the application. "Swifty" wrote: |
|
Thread Tools | |
Display Modes | |
|
|