Re: Error:Invalid procedure call or argument
From: Dirk Goldgar (dg_at_NOdataSPAMgnostics.com)
Date: 06/18/04
- Next message: Douglas J. Steele: "Re: Recordset criteria from a form"
- Previous message: Sean Henry: "Recordset Criteria"
- In reply to: Matt Weyland: "Error:Invalid procedure call or argument"
- Next in thread: Matt Weyland: "Re: Error:Invalid procedure call or argument"
- Reply: Matt Weyland: "Re: Error:Invalid procedure call or argument"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 18 Jun 2004 12:26:04 -0400
"Matt Weyland" <anonymous@discussions.microsoft.com> wrote in message
news:1e6a801c4554c$b0b3b7e0$a401280a@phx.gbl
> I keep getting this error Error number 5 and and Error
> Number 0 everytiime I execute this code:
>
> Private Sub Update()
> On Error GoTo ErrHand
> SQL = "UPDATE tblMemo SET subject = " & AddQuotes
> (mSubject) & "," & _
> "dateReceived =#" & mDateRcvd & "#, " & _
> "URL = " & AddQuotes(mQNetURL) & ", " & _
> "DateEntered = #" & mDateEntered & "#, " & _
> "ServerLocation =" & AddQuotes(mServerLocation) & _
> " WHERE MemoID = " & AddQuotes(MemoID)
>
> Set DB = CurrentDb
> DB.Execute SQL, dbFailOnError 'this is where this fails
> 'Set DB = Nothing
> ErrHand:
> 'If Err.Number = 5 Or Err.Number = 0 Then Exit Sub
> 'Stop
> Err.Raise Err.Number, Err.Source, Err.Description
> MsgBox "Error: Class: Memo" & vbCrLf & "Method: Private-
> Insert" & vbCrLf & Err.Number & ":" & Err.Description
>
>
> End Sub
>
> I can't seem to figure out why this keeps occuring.
> Following is an example of the completed SQL string. Which
> when pasted into the SQL designer executes with no errors,
> and the code is updating the source table eventhough this
> is returning an error.
>
> UPDATE tblMemo SET subject = "This is the
> subject",dateReceived =#6/16/2004#, URL = "fff",
> DateEntered = #6/16/2004 6:29:35 PM#, ServerLocation
> ="C:\Work\Training Document.doc" WHERE MemoID = "04-125-CA"
>
> I duplicated this code across several classes and it
> everyone is generating the same error. I am quite sure
> that I have the correct libraries referenced, but can't
> seem to figure this out.
>
> Any assistance anyone can provide on this will be greatly
> appreciated.
Because you have no Exit Sub statement before your error-handling code,
the sequence of execution "falls through" to that error handler even
when no error has occured. Then your error-handling code tries to raise
error 0, which is not valid and causes error 5 (invalid procedure call
or argument), and then your own message is displayed showing error 0.
Change it like this:
'----- start of revised part of code -----
Set DB = CurrentDb
DB.Execute SQL, dbFailOnError
Exit_Point:
Set DB = Nothing
Exit Sub
ErrHand:
MsgBox _
"Error: Class: Memo" & vbCrLf & "Method: Private-Insert" & _
vbCrLf & Err.Number & ":" & Err.Description
Err.Raise Err.Number, Err.Source, Err.Description
Resume Exit_Point
End Sub
'----- end of revised part of code -----
-- Dirk Goldgar, MS Access MVP www.datagnostics.com (please reply to the newsgroup)
- Next message: Douglas J. Steele: "Re: Recordset criteria from a form"
- Previous message: Sean Henry: "Recordset Criteria"
- In reply to: Matt Weyland: "Error:Invalid procedure call or argument"
- Next in thread: Matt Weyland: "Re: Error:Invalid procedure call or argument"
- Reply: Matt Weyland: "Re: Error:Invalid procedure call or argument"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|