Error trap not trapping

elizabeth · Apr 28, 2000

I have a form which has a button to open a related form. The 1st form is an inventory item, the 2nd form is the PO for that item (and possibly add'l items). In many cases, no PO has not been entered yet. If I try to open the form based on a linking POID, I get Run-time error '3075': Syntax error (missing operator) in query expression 'QuoteID =' I thought I had fixed this with the following code months ago, but just noticed this is not working. Any ideas? TIA. Private Sub cmdPO_Click() On Error GoTo Err_cmdPO_Click     Dim stDocName As String     Dim stLinkCriteria As String     stDocName = "frmPO"     DoCmd.RunCommand acCmdSaveRecord     stLinkCriteria = "[POID]=" & Me![POID]     DoCmd.OpenForm stDocName, , , stLinkCriteria Exit_cmdPO_Click:     Exit Sub Err_cmdPO_Click:     If Err.Number = 3075 Then         MsgBox "Enter a value in this field to display details."         Resume Exit_cmdPO_Click     Else         MsgBox Err.Description         Resume Exit_cmdPO_Click     End If      End Sub

Cornerstone · Apr 28, 2000

Well that is a doozie (sp?)  Hmmm. I assume the button you are clicking on to open the form is still called cmdPO. Are any other subs coming into play that you are not showing? This button click is not being called by another button click is it? Silly but change the error trap to this: Select Case Err.Number Case 3075    MsgBox "Enter a value in this field to display details."    Resume Exit_cmdPO_Click Case Else    MsgBox Err.Description    Resume Exit_cmdPO_Click End Select     I would also test an err.raise in there to see if you can raise your own error. Your code looks like it should be working. You can also try to delete the button and recreate it. end select

elizabeth · Apr 28, 2000

1. Yes button is named cmdPO. 2. No, this is the only code involved. 3. Tried the case stmt, same result (nada), same message. 4. Tried err.raise - if i put it after the line:     DoCmd.OpenForm stDocName, , , stLinkCriteria I get same result, same message. If I put it after that line, I get the the same number, but slightly more generic message: Application-defined or object-defined error. Thanks for the suggestions - I'll try anything! Any other ideas? BTW, this is happening on 3 separate buttons that open 3 similar forms. In the meantime I'll try recreating the button just in case there was some corruption.

elizabeth · Apr 28, 2000

GUESS WHAT! I found this code still works perfectly in my 97 version of this application! It is exactly the same. I also deleted and recreated the button in case t was corrupted but it still doesn't work. Is there any differences in error trapping in version 2000?

Cornerstone · Apr 28, 2000

Did you import the form from the 97 database? (bad) Did you convert the 97 database to 2000? (good) Have you tried to recreate the Form itself? (ouch) Do you have all the References that you need set in Tools, References?

Guest_imported · Apr 28, 2000

1. converted (good)! But while I'm at it I'll try importing, just in case! 2. Big big ouch. Complex form. But I'll do it if I can't find any other solution... 3. Are you aware of any particular reference I need for this code? Currently I've got references set to: Visual Basic for Applications MS Access 9.0 Lib OLE Automation MS DAO 3.6 Lib MS VBA for extensibility 5.3

elizabeth · May 3, 2000

Solved. My own dumb fault for somehow turning on the "Break on All Errors" option  instead of "Break on Unhandled Errors". It's under Tools/Options/General -this option only displays when you are actually in the VB code editor. Time for the Ginko Biloba!

Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Error trap not trapping

elizabeth

IS-IT--Management

Cornerstone

MIS

elizabeth

IS-IT--Management

elizabeth

IS-IT--Management

Cornerstone

MIS

Guest_imported

New member

elizabeth

IS-IT--Management

Similar threads

Part and Inventory Search

Sponsor