Access VBA for Delete Record on multiple Tables

I have a button on an Access Form.  What I would like to do is, upon clicking this button, the current record gets deleted.  The issue I am having is that this record exists in multiple Tables. For example, each of my records is given a unique identifier 'InterviewID.'  I have 4 records:  100, 101, 102 and 103.  Currently, I am working on record 102—and I'd like to delete this record within all Tables.  For example:

Table1
Primary Key:  InterviewID  [102]

Table2
Primary Key:  InterviewID  [102]

Table3
Primary Key:  InterviewID  [102]
I've been using the following code—but it only seems to delete the record for Table1 (InterviewID still exists in Table2 and Tabl3).
If MsgBox("Do you wish to delete this record?", vbYesNo, "Delete Confirmation") = vbYes Then
   If MsgBox("Are you SURE you want to delete this record?" & vbCrLf & _
    "This will permanently delete the record.", vbYesNo, "2nd Delete Confirmation") = vbYes Then
         DoCmd.RunCommand acCmdDeleteRecord
   End If
End If

Does anyone know how to modify this code so that it deletes the current record in all tables?
mdstallaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gustav BrockCIOCommented:
Go to Database Tools, Relations.
Set up relations between table1 - table2 and table1 - table2. For each relation set referential integrity to Delete.

DO make a backup first.

/gustav
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Setting up relations for tables as gustav mentioned is one approach.   Just be careful with that; you can end up deleting a whole lot of data you don't mean to very quickly as that will work not only through a form but also through query and table views.

 The other method is to issue an actual SQL delete statement (either via query or directly - DELETE * FROM <table> WHERE <condition>) on each table  that you want to delete from.  There are cases where you may want to delete from some, but not all that you may have setup relation ships with depending on the circumstances.

  Some view the second as somewhat of  a "protection" because you need to go through the form to get rid of the data.   Relations are really the right way to go, but more often than not, it leads to people deleting a lot of things they don't intend to.

Jim.
0
Rey Obrero (Capricorn1)Commented:
revising your codes, without setting relationships with your tables


If MsgBox("Do you wish to delete this record?", vbYesNo, "Delete Confirmation") = vbYes Then
    If MsgBox("Are you SURE you want to delete this record?" & vbCrLf & _
     "This will permanently delete the record.", vbYesNo, "2nd Delete Confirmation") = vbYes Then
          'DoCmd.RunCommand acCmdDeleteRecord
          CurrentDb.Execute "delete * from table1 where interviewid=" & Me.txtInterviewID
          CurrentDb.Execute "delete * from table2 where interviewid=" & Me.txtInterviewID
          CurrentDb.Execute "delete * from table3 where interviewid=" & Me.txtInterviewID
         
    End If
 End If


just change "txtInterviewID" with the actual name of the control for InterviewID
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Gustav BrockCIOCommented:
That will make the record appear as #Deleted on the form. Not very nice.

Whatever, the issue smells:

> The issue I am having is that this record exists in multiple Tables.

It sounds like you should study some basic material on relational databases and normalisation. Just bing/google on the topic.

/gustav
0
Rey Obrero (Capricorn1)Commented:
not if you do a requery after deletion
0
Gustav BrockCIOCommented:
Then you waste time during the requery, and you loose the current record and has to relocate the recordset after the requery.

/gustav
0
mdstallaAuthor Commented:
I used Rey's code but got an error:

Runtime Error 3075
Syntax Error (Missing Operator) in query expression InterviewID=".

Any clue what the hold-up could be?

If I click 'End' the record appears to delete as desired.
0
Rey Obrero (Capricorn1)Commented:
post the actual codes that you used
0
Rey Obrero (Capricorn1)Commented:
is the field  InterviewID  Text or Number data type ?
0
mdstallaAuthor Commented:
Rey:

Here's the actual code I used.  InterviewID is a Number for each Table.  You should note that this error only appears to be related with the last table "TblAgentNos"

If MsgBox("Do you wish to delete this record?", vbYesNo, "Delete Confirmation") = vbYes Then
     If MsgBox("Are you SURE you want to delete this record?" & vbCrLf & _
      "This will permanently delete the record.", vbYesNo, "2nd Delete Confirmation") = vbYes Then
           'DoCmd.RunCommand acCmdDeleteRecord
           CurrentDb.Execute "delete * from table1 where interviewid=" & Me.InterviewID
           CurrentDb.Execute "delete * from table2 where interviewid=" & Me.InterviewID
           CurrentDb.Execute "delete * from table3 where interviewid=" & Me.InterviewID
           CurrentDb.Execute "delete * from table4 where interviewid=" & Me.InterviewID
           CurrentDb.Execute "delete * from table5 where interviewid=" & Me.InterviewID
           CurrentDb.Execute "delete * from table6 where interviewid=" & Me.InterviewID
           CurrentDb.Execute "delete * from table7 where interviewid=" & Me.InterviewID
           CurrentDb.Execute "delete * from table8 where interviewid=" & Me.InterviewID
           CurrentDb.Execute "delete * from table9 where interviewid=" & Me.InterviewID
           CurrentDb.Execute "delete * from tblInterviewMain where interviewid=" & Me.InterviewID
            CurrentDb.Execute "delete * from tblAgentNos where interviewid=" & Me.InterviewID

           
     End If

  End If
0
Gustav BrockCIOCommented:
Then in your table tblAgentNos you have no field named interviewid.

But having the same info in 11 tables is very weird. It needs a redesign.

/gustav
0
Rey Obrero (Capricorn1)Commented:
run a compact and repair then
check your table  tblAgentNos  by running this query

select * from  blAgentNos where interviewid= 102

change 102 with the interviewID that you deleted from the other tables.

post back the result
0
mdstallaAuthor Commented:
Here's what my code looks like based on your instructions (let me know if I did this wrong):

If MsgBox("Do you wish to delete this record?", vbYesNo, "Delete Confirmation") = vbYes Then
     If MsgBox("Are you SURE you want to delete this record?" & vbCrLf & _
      "This will permanently delete the record.", vbYesNo, "2nd Delete Confirmation") = vbYes Then
           'DoCmd.RunCommand acCmdDeleteRecord
           CurrentDb.Execute " select * from  TblAgentNos where interviewid= 28"
           End If
           End If

I'm getting an error message that says:

Run Time Error 3065
Cannot execute a select query
0
Rey Obrero (Capricorn1)Commented:
what I meant is you create a new query in design view using TblAgentNos

Field   *                        | interviewid
Table TblAgentNos    

Criteria                            28
0
mdstallaAuthor Commented:
Oh, Okay-- sorry.

I did what you said using the Criteria 34.  I've attached the Query with its returns:
accessspreadsheet.xlsx
0
Rey Obrero (Capricorn1)Commented:
what is the record source of the form you are using here?

if the record source is table1, try doing this

If MsgBox("Do you wish to delete this record?", vbYesNo, "Delete Confirmation") = vbYes Then
      If MsgBox("Are you SURE you want to delete this record?" & vbCrLf & _
       "This will permanently delete the record.", vbYesNo, "2nd Delete Confirmation") = vbYes Then
            'DoCmd.RunCommand acCmdDeleteRecord
           
            CurrentDb.Execute "delete * from tblAgentNos where interviewid=" & Me.InterviewID
            CurrentDb.Execute "delete * from tblInterviewMain where interviewid=" & Me.InterviewID

            CurrentDb.Execute "delete * from table2 where interviewid=" & Me.InterviewID
            CurrentDb.Execute "delete * from table3 where interviewid=" & Me.InterviewID
            CurrentDb.Execute "delete * from table4 where interviewid=" & Me.InterviewID
            CurrentDb.Execute "delete * from table5 where interviewid=" & Me.InterviewID
            CurrentDb.Execute "delete * from table6 where interviewid=" & Me.InterviewID
            CurrentDb.Execute "delete * from table7 where interviewid=" & Me.InterviewID
            CurrentDb.Execute "delete * from table8 where interviewid=" & Me.InterviewID
            CurrentDb.Execute "delete * from table9 where interviewid=" & Me.InterviewID

            CurrentDb.Execute "delete * from table1 where interviewid=" & Me.InterviewID
           
      End If

   End If
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mdstallaAuthor Commented:
You're the Man Rey!  That worked perfectly--thanks for all of your help!
0
Rey Obrero (Capricorn1)Commented:
yeah that did it, but you have to rethink the design of your table..

see this link Data Normalization
0
mdstallaAuthor Commented:
Really?  Is my design technique really that messed up?  I ask that question inquisitively… as a Rookie Database Designer, not as a cocky-bastard.

It would seem to me that if I have X-number of Tables, each of which contains Fields with information that needed to be associated with the same, appropriate, respective Record… there would have to be some 'common denominator….'  a common Field in which each of these Tables could be related/connected.

For each Table, the first Field I created (The Unique Identifier--The Key) was "Interview ID."  By creating this… I was able to create Relationships… saying "Interview ID in Table1 is the same as Interview ID in Table2.
Why is this erroneous?
What would be a more prudent way of linking Tables?
0
Gustav BrockCIOCommented:
There may not be. We can't tell without knowing the schema.

Again, if relations are properly set up, this would be a much easier and faster method:

http://www.experts-exchange.com/Database/MS_Access/Q_28575598.html#a40484655

/gustav
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.