Empty Record being created
I have a form where the user will update the recordset, and after closing the form, there is a blank record (other than key) created.
I have looked at the events on the form nothing other than form refreshes being performed. I can not find any reason why an additional record is created when the user updates an existing record via the form
I have looked at the events on the form nothing other than form refreshes being performed. I can not find any reason why an additional record is created when the user updates an existing record via the form
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
You can add "Required" property to any field in your table. After this you will get an error when empty record will be added. Select "debug" and you will see code, where record is added. You can use "On error resume next". In this case record will be not added to table with required field
Probably you have something "extra" in your code that is "pushing' the empty data....breakpoint/debug your data along with constantly querying the underlying table to see when the empty record is inserted....
Do you have any code in the OnCurrent even?
And if so ... are you setting any 'default values' or otherwise ?
" nothing other than form refreshes being performed"
Can you elaborate ?
And if so ... are you setting any 'default values' or otherwise ?
" nothing other than form refreshes being performed"
Can you elaborate ?
Refresh has the side effect of forcing the current record to be saved if it is dirty. Always use an explicit save command if that is your intention. The standard is DoCmd.RunCommand acCmdSaveRecord. An alternate that circumvents a particular problem which I have never encountered is. Me.Dirty = False.
Given the symptoms, your code is dirtying the record and the Refresh is forcing it to be saved. I use the method suggested by als. Setting declarative RI on the table means that regardless of what prompts the update, the database engine will enforce your rules.
Given the symptoms, your code is dirtying the record and the Refresh is forcing it to be saved. I use the method suggested by als. Setting declarative RI on the table means that regardless of what prompts the update, the database engine will enforce your rules.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial