Error 3464 Reserved Error

[e.badin]

As the title says, I'm running into this error while trying to open a report:

Error 3464 Reserved Error

here is the code (I trimmed it a little):

Private Sub LKA2_RUN_BTN_Click()

DoCmd.Hourglass True
DoCmd.SetWarnings False

On Error GoTo Err_Handler
    'Purpose:  Open the report filtered to the items selected in the list box.
    
    Dim varItem As Variant      'Selected items
    Dim strWhere As String      'String to use as WhereCondition
    Dim strDescrip As String    'Description of WhereCondition
    Dim lngLen As Long          'Length of string
    Dim strDelim As String      'Delimiter for this field type.
    Dim strDoc As String        'Name of report to open.
    Dim strsql As String
    
    strDelim = """"
    strDoc = "TDL_REPORT_MWC"
    strWhere = ""
    strDescrip = ""
    DoCmd.OpenReport strDoc, acViewPreview, WhereCondition:=strWhere, OpenArgs:=strDescrip
    

DoCmd.SetWarnings True
DoCmd.Hourglass False

Exit_Handler:
    Exit Sub

Err_Handler:
    If Err.Number <> 2501 Then  'Ignore "Report cancelled" error.
        MsgBox "Error " & Err.Number & " - " & Err.Description, , "cmdPreview_Click"
    End If
    Resume Exit_Handler
End Sub

Edit: I noticed the same code works perfect in Access 2007...

[GinaWhipp]

Try changing...

DoCmd.OpenReport strDoc, acViewPreview, WhereCondition:=strWhere, OpenArgs:=strDescrip

...to this...

 
DoCmd.OpenReport strDoc, acViewPreview, ,WhereCondition:=strWhere, , OpenArgs:=strDescrip

I believe you are missing a some commas. For further explanation see...
http://www.blueclaw-db.com/docmd_openreport.htm

[boblarson]

Try changing...

DoCmd.OpenReport strDoc, acViewPreview, WhereCondition:=strWhere, OpenArgs:=strDescrip

...to this...

 
DoCmd.OpenReport strDoc, acViewPreview, ,WhereCondition:=strWhere, , OpenArgs:=strDescrip

I believe you are missing a some commas. For further explanation see...
http://www.blueclaw-db.com/docmd_openreport.htm

Gina:

You don't need the commas when using the argument names. So if you DON'T use the argument names (i.e. WhereCondition or OpenArgs) then you need the commas. If you use argument names then you don't So their code is correct. But I am wondering why they are setting the strWhere to "" (an empty string) which is an invalid filter. strWhere should NOT be used if it is going to be simply an empty string.

So e.badin - why are you doing that?

[GinaWhipp]

@Bob,

I always thought that you needed the *space holders* if you are using only some of the arguments names but not all. Hope I explained that correctly... So if I were only going to use OpenArg or strWhere then I would still need the commas and the ywould just default to the Default.

[boblarson]

@Bob,

I always thought that you needed the *space holders* if you are using only some of the arguments names but not all. Hope I explained that correctly... So if I were only going to use OpenArg or strWhere then I would still need the commas and the ywould just default to the Default.

Well, it is like this. If you are going to use any named arguments you need to provide anything else that follows with named arguments. You can use commas up to the point of a named argument but what's the point. The point to using named arguments is you can eliminate all of the , , , , , , type of stuff.

So you can do:

DoCmd.OpenForm "FormNameHere", OpenArgs:=strSomething

DoCmd.OpenForm "FormNameHere', WindowMode:=acAdd, OpenArgs:=strSomething

DoCmd.OpenForm "FormNameHere", OpenArgs:=strSomething, WindowMode:=acEdit, WhereCondition:=strWhere

The benefits to named arguments is that you can tell exactly what you're dealing with, you can put them in any order you choose, and you can avoid long lines of commas.
or

[GinaWhipp]

@Bob,

Hmmm, I guess you can teach an old dog(ette) new tricks! Thanks!

[boblarson]

@Bob,

Hmmm, I guess you can teach an old dog(ette) new tricks! Thanks!

No worries as I learn new stuff all of the time as well. There is so much to learn about Access, I don't know if anyone really knows it all. I know of a few people who I would think may be close or might know it all but it is rare.