Close - Ignore validation

[School Boy Error]

Hello, I have a problem in that I have a close button on a form - this loads an embedded macro that simply closes the windows (set warnings is set to "no").If the form is blank and the user clicks close, it works brilliantly. If the user has half filled in the form, it then says the x, y and z fields can't be empty, cannot save the record at this time etc. How do I set it so if the user clicks close, any input is ignored and the form is closed?Thank you!

[isladogs]

One way is to have a CheckComplete procedure which runs in the close button code

The idea is that it would check a list of controls that need to be filled before the form can be closed.
I prefer to then pop up a message listing unfilled controls and changing their background colour.
However if preferred, you could use it to empty any filled controls in a partly completed record then close the form

Suggest you use vba procedure rather than an embedded macro

[School Boy Error]

Thank you. Is there a simple way in vba then of just closing the form and ignoring all the values?

[Micron]

How do I set it so if the user clicks close, any input is ignored and the form is closed?

IMHO, this is the incorrect approach. There is a basic standard that's all about how Windows apps should be laid out and behave, and this approach doesn't fit. Mind you, I'm sure I'm guilty of not adhering to that standard 100% as it is quite involved. Anyway, my answer would be don't do what you are doing as Close has one meaning, and Cancel has another. In the simplest terms, your form should have a Save/Close button and a Cancel button and not be too close together. Should be fairly obvious as to what they do. You choose to permit the cancellation of the Cancel if a form is partially filled out or not by way of design. I would hate to lose a lot of work if I clicked the wrong one. Point is that you have to make the decision as to whether or not that's warranted or just a pesky prompt. Another choice is Save, Close, Cancel, and a prompt to force a conscious decision to not save before closing. However, the Save without closing is more complex, but it does allow you to save a partial record and pause (or leave and come back) as long as the minimum required fields are filled in.

[School Boy Error]

I understand what you're saying. Thank you for the tips.

[School Boy Error]

Is there any VBA script for clearing a form or would I need to specify each control value individually?

[isladogs]

I also think this isn't the way to proceed and suggested a better alternative in my first reply.

If you really want to do this, you either need to list all controls individually or loop through each in turn to set to a ZLS
Something like this should work but test it out in a non critical situation first!

Dim ctrl As Access.Control

For Each ctrl In Screen.ActiveForm.Controls
      If ctrl.ControlType = acTextBox Then ctrl = ""
Next ctrl

Note its been limited to textboxes so label captions aren't cleared

[School Boy Error]

Thank you - I know not ideal but I'm no expert - unfortunately not even a novice so this worked for me:

Private Sub close_form_Click()On Error Resume NextDim ctl As ControlFor Each ctl In Me.Controls    If ctl.ControlType = acTextBox Then ctl = NullNextSet ctl = NothingDoCmd.CloseEnd Sub

[isladogs]

It's more convoluted than it needs to be.
The code I gave is more efficient though you can use Null rather than "" if you prefer

[Micron]

Wouldn't Me.Undo be simpler?

[isladogs]

Wouldn't Me.Undo be simpler?

Definitely yes but only if all the controls are bound
The other method works for both bound & unbound

[Micron]

If any were not bound, the warning about saving a record wouldn't apply to them so I don't see how that's relevant. Unbound controls don't cause warnings about records, do they? Close a form full of unbound controls and nothing happens. No partial record (because they're not bound). No prompts or warnings. Reopen form and it's blank.

[isladogs]

True but I just went for a method that cleared both types of control.
I'm not saying its a better approach & I wouldn't dream of mentioning nit-picking either!

Me.Undo is almost certainly absolutely perfect for the OP's needs. I commend that approach to the OP

We both agree that this isn't the best way to proceed when closing a partially completed form