Upgraded to Accesss 2003 SP2 and now app doesn't work

[MemphisVBA]

I have an application that worked fine until the user's PC was upgraded. She has the same version of Access (2003) but the service pack level is now SP2. The other users are all at SP1 and the app works fine for them. On the upgraded user's machine, it only partially works.

There are two parts of the application that don't work.

The first part is basically this: a row in a listbox is clicked - this is the code (that doesn't run) for the onclick event:

Private Sub lstReadyForAP_Click()

    DoCmd.OpenReport "rptNational", acPreview
    DoCmd.OutputTo acOutputReport, "rptNational", acFormatSNP, "N:\Finance\CarrierNBS\invoices\" & lstReadyForAP.Value & "-N.snp", 0

    Dim intResp As Integer
    Dim strQues As String
    
    strQues = "Do you want to export invoice #" & lstReadyForAP & vbCrLf & " to the Accounts Payable file?"
    intResp = MsgBox(strQues, vbYesNo, "Send invoice #" & lstReadyForAP.Value & " to AP?")
    
    If intResp = vbYes Then GoTo SendToAP
    If intResp = vbNo Then GoTo NotYet


SendToAP:
    Dim strSQL As String
    strSQL = "UPDATE tblInvoice SET tblInvoice.senttoap = 1, tblInvoice.datesenttoap = date() WHERE (([lstReadyForAP]=[tblInvoice]![InvoiceNo]));"
        DoCmd.RunSQL strSQL, 0



        Me.Refresh
        
Exit Sub

NotYet:

        

End Sub

The second part of the application that doesn't work on the upgraded (SP2) machince occurs when the user presses a button to open a summary report. Here is the onclick event code (that isn't working):

Private Sub cmdShowBatchSummaryReport_Click()
On Error GoTo Err_cmdShowBatchSummaryReport_Click

    Dim stDocName As String

    stDocName = "rptZfileBatchSummary"
    DoCmd.OpenReport stDocName, acPreview

Exit_cmdShowBatchSummaryReport_Click:
    Exit Sub

Err_cmdShowBatchSummaryReport_Click:
    MsgBox Err.Description
    Resume Exit_cmdShowBatchSummaryReport_Click
    
End Sub

what is weird (about the second problem) is that there are other buttons that open other reports that work fine.

I am only guessing that the SP1 vs. SP2 is where the problem lies - I did also notice that her ADO version went from 2.7 to 2.8

I contacted our IT guys - asking if they could "roll back" the SP2 - this is the reply I got:

"Right now she has MDAC 2.8 sp1. Uninstalling access and rolling it back a SP will not fix the problem. MDAC will have to be rolled back and there is no easy process to do this. I will have to do some research to see how we can get this done."



Can someone please tell me where to start troubleshooting?

Thanks in advance -
Patrick in Memphis

 

[LNBruno]

First off, I'd suggest setting a breakpoint in the code to determine exactly where the error is being generated.

< M!ke >