Delete record if no records exist in sub-form
I have a form with a sub-form. If the user has not entered any records in the sub-form and clicks the [Close Form], (a customer command button on the main form), I want the main record to be deleted without warning.
How can I do this?
How can I do this?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
try:
Private Sub btnClose_Click()
ID = Me.txtID.Value 'or something you can refer to present the unique main record
If Me.yourSubform.Form.Record
CurrentDB.execute "Delete from yourMaintable where id = " & ID
End If
End Sub
Private Sub btnClose_Click()
ID = Me.txtID.Value 'or something you can refer to present the unique main record
If Me.yourSubform.Form.Record
CurrentDB.execute "Delete from yourMaintable where id = " & ID
End If
End Sub
You can just delete the record:
Private Sub Form_Unload(Cancel As Integer)
If Me!NameOfSubformControl.Form.RecordsetClone.RecordCount = 0 Then
DoCmd.RunCommand acCmdDeleteRecord
End If
End Sub
Also, to prevent the dialogue box:
Private Sub Form_BeforeDelConfirm(Cancel As Integer, Response As Integer)
Response = acDataErrContinue
End Sub
Note that things like this go against basic referential integrity rules, and may be hard to control when your design becomes more complex.
In a standard situation it is fairly common for a Parent record to be created and not have any Child records.
(The problem arises if you have child records with no parent (orphaned records))
For example, A person will become a Patient and not necessarily make an appointment for a "Visit" for a few weeks.
You can become a student at a school and not register for classes until the next semester.
Your users may wonder why a customer they created yesterday, ...is not showing up today?
Is this new "rule" to be universal with all Parent/Child relationships?
If not, then it will be confusing to users as to when a parent record will persist, and when it will "disappear"
As usual, an explanation of why this is needed is always helpful.
Again, deleting Parent records automatically (and without notice) is something that is not commonly done.
JeffCoachman
In a standard situation it is fairly common for a Parent record to be created and not have any Child records.
(The problem arises if you have child records with no parent (orphaned records))
For example, A person will become a Patient and not necessarily make an appointment for a "Visit" for a few weeks.
You can become a student at a school and not register for classes until the next semester.
Your users may wonder why a customer they created yesterday, ...is not showing up today?
Is this new "rule" to be universal with all Parent/Child relationships?
If not, then it will be confusing to users as to when a parent record will persist, and when it will "disappear"
As usual, an explanation of why this is needed is always helpful.
Again, deleting Parent records automatically (and without notice) is something that is not commonly done.
JeffCoachman
Premium Content
You need an Expert Office subscription to comment.Start Free Trial