Could be a long shot but try it without de optional arguments...
I assume these are append queries..

DoCmd.OpenQuery “billcemeteryyear”
DoCmd.OpenQuery “billcemeteryhalfyear”

Maurice

Well, that code doesn't much resemble what I posted... <g>

It's not SQL (the language of queries); it's VBA, Visual Basic for
Applications, the language of modules. You had posted some VBA code which
executes two queries; I posted some alternative VBA code to execute those same
two queries.

Here's what I'd suggest that you use. Change the button name from Command29 to
something meaningful - cmdRunBills let's say - just so you can understand the
code yourself later.

Private Sub cmdRunBills_Click()    
Dim db As DAO.Database ' define a Database object
Dim qd1 As DAO.Querydef ' define two Querydef objects
Dim qd2 As DAO.Querydef
On Error GoTo Proc_Error ' set up an error trap
Set db = CurrentDb ' set the Database object to the current database
Set qd1 = db.Querydefs("billcemeteryyear") ' select your first action query
qd1.Execute, dbFailOnError ' run it; if there's an error it will be trapped
MsgBox "Bill Cemetery Year query affected " & qd1.RecordsAffected & " records"
Set qd2 = db.Querydefs("billcemeteryhalfyear") ' select the next query
qd2.Execute, dbFailOnError ' run it
MsgBox "Bill Cemetery  Half-year affected " & qd2.RecordsAffected & " records"
Proc_Exit:
On Error Resume Next ' ignore any errors in the cleanup
Set qd1 = Nothing ' clean up after yourself
Set qd2 = Nothing
Exit Sub
Proc_Error: ' any errors come here
                 ' Display the error on the screen
 MsgBox "Error " & Err.Number & " in cmdRunBills_Click:" & vbCrLf _
              & Err.Description
 Resume Proc_Exit ' after displaying the error, just quit
End Sub

COpy this entire program into the Click event code of your command button;
select Debug... COmpile; correct any errors or post back for help doing so.

            John W. Vinson [MVP]