Saving and cancelling data input in a form

[redekopp]

Hey there, I think I've got myself confused a bit. I have created simple forms that pop up to add new items to a specific table. Example being adding a new interior colour to the list of interior colour choices.

you click the "add" button the form opens to a new record. you type in an interior colour in the intcolour field and click save or cancel. What am I doing so that the save and cancel button actually either allows or denies this new entry from sticking?

right now im doing:

DoCmd.Close acForm, "frmInteriorColour", acSaveYes

for the save button
and

DoCmd.Close acForm, "frmInteriorColour", acSaveNo

for the cancel button

No matter which one u choose if you have typed something into the intcolour field its been added to the table.

How do I make it based on the save and cancel buttons only?

Thanks

[June7]

The acSaveYes and acSaveNo have nothing to do with saving data, they pertain to saving design changes of the form. This is because code can be utilized to change some properties during runtime. But usually it is not desired to make these changes permanent, hence acSaveNo when closing the form.

Data is committed to table when closing form, moving to another record, or running code. One code example is: DoCmd.RunCommand acCmdSaveRecord

Using a button to abort record commitment can be tricky. This might involve command to 'undo' the inputs or somehow pass value to form BeforeUpdate event as parameter to Cancel.

[redekopp]

Would it work if I make the cancel button clear the fields before closing? or would it save moving from one field to the next, if there is more then one data field on the form?


EDIT: I tried this, but all it does is make the one field have a null entry, still creates the automatic ID for the colours. sigh.
DOUBLE EDIT: DoCmd.RunCommand acCmdUndo fixed my issue. just adding that before the close command.. Thanks for the help June!