Class module getting a 2046 error

[GraeagleBill]

I have a class module where I'm getting a:

Option Compare Database
Option Explicit
Dim ShellString As String
Dim ShellRC As Variant
Public WithEvents Target As Access.CommandButton


Private Sub Target_MouseDown(Button As Integer, Shift As Integer, X As Single, Y As Single)


If Me.Target.Name = "cmdPrintRegistry" Then
    strCurRptsPath = "c:\Asilomar\PDF-Reports"
    strCurPDFName = strCurRptsPath & "\ForestLodgeRegistry.pdf"
    
    DoCmd.OpenReport "rptEntireRegister", acViewPreview, , , acHidden
    DoCmd.OutputTo acOutputReport, "rptEntireRegister", acFormatPDF, strCurPDFName
    DoCmd.Close acReport, "rptEntireRegister", acSaveNo
    
    ShellString = "c:\Windows\Explorer.exe " & """" & strCurPDFName & """"
    ShellRC = Shell(ShellString, 4)
End If


End Sub

I simply want to write a report to a pdf file without previewing the report on the screen. The mode of the form with the command button is in Dialog mode, but I have other class modules in much the same condition, so I'm at a loss as to why the OutputTo would be unavailable.

Any ideas?

[Micron]

Haven't done this in a while, so have to ask - why open the report? IIRC you don't have to, and if you're not going to review it first there's no need to open it at all?
If sticking with the current approach, I guess I'd try DoEvents between the output and the close.

[GraeagleBill]

so have to ask - why open the report?

Same issue as described here. See posts 5,6 & 7
https://www.accessforums.net/showthread.php?t=84719

I don't follow your suggestion? The 2046 occurs on the OutputTO trying to write the open report to a pdf file, so DoEvents would be after the error had already occurred.

[Micron]

The 2046 occurs on the OutputTO trying to write the open report to a pdf file

I was thinking possibly because it just closed in the very next line? Perhaps not since this works elsewhere. Of course, you would have stepped through this code, not to see which line errors but to see if timing was an issue, because by now you would be well aware of that troubleshooting technique. My guess was based on you only mentioning the error, which does not prove that there is anything wrong with output line itself.

[Welshgasman]

I take it you can create files in that folder?

[GraeagleBill]

I substituted the troublesome report name in the app's form that deals with all the other reports that use a common class module and the same code in the OP works fine. There has to be something peculiar with the host form in this case.

Here's the code from the form's OnLoad that creates the CommandButton collection in the host form. I'll try changing the collection to the form's labels, let the command button masquerade as such and use the common class module to handle the pdf creation. That then, should match the substitution I tried earlier.

Dim L As clsCommandButton
Dim C As Control


'Keep an instance of the clsCommandButton for each command button in the form.
Set mcolCmdButns = New Collection
For Each C In Me.Controls
    If TypeName(C) = "CommandButton" Then
        C.OnClick = "[Event Procedure]"
        C.OnMouseDown = "[Event Procedure]"
        C.ControlTipText = "Click on " & C.Name
        Set L = New clsCommandButton
        Set L.Target = C
        mcolCmdButns.Add L, C.Name
    End If
Next C

[GraeagleBill]

Yes, see post #6

[GraeagleBill]

As I somewhat expected, the idea stated in #6 really doesn't change anything switching from a command button to a label if the host form's mode is such that OutputTo isn't available. I'll keep looking.

[Minty]

PMFJI - But you only need to open it (the report) first to apply a dynamic filter.
Which if read you code correctly you are not doing in this instance.

So I could be a bit confused?

[Welshgasman]

PMFJI - But you only need to open it (the report) first to apply a dynamic filter.
Which if read you code correctly you are not doing in this instance.

So I could be a bit confused?

Me too, as according to the linked post 'works like a champ'
All that was

Private Sub pdfDirect(rptName As String, CtrlName As String)


strpdfFile = Forms("frmDocuments").Controls(Replace(CtrlName, "lbl", "tb"))
strCurPDFName = strCurRptsPath & "\" & strCurRetreat & "\" & strpdfFile & ".pdf"


DoCmd.OpenReport rptName, acViewPreview, , , acHidden
DoCmd.OutputTo acOutputReport, rptName, acFormatPDF, strCurPDFName
DoCmd.Close acReport, rptName, acSaveNo


End Sub

[GraeagleBill]

Now I'm confused, see OP code showing the open report to effect the dynamic filtering

Option Compare Database
Option Explicit
Dim ShellString As String
Dim ShellRC As Variant
Public WithEvents Target As Access.CommandButton


Private Sub Target_MouseDown(Button As Integer, Shift As Integer, X As Single, Y As Single)


If Me.Target.Name = "cmdPrintRegistry" Then
    strCurRptsPath = "c:\Asilomar\PDF-Reports"
    strCurPDFName = strCurRptsPath & "\ForestLodgeRegistry.pdf"
    
    DoCmd.OpenReport "rptEntireRegister", acViewPreview, , , acHidden  <<<<<<<<<< Open report to populate the dynamics
    DoCmd.OutputTo acOutputReport, "rptEntireRegister", acFormatPDF, strCurPDFName
    DoCmd.Close acReport, "rptEntireRegister", acSaveNo
    
    ShellString = "c:\Windows\Explorer.exe " & """" & strCurPDFName & """"
    ShellRC = Shell(ShellString, 4)
End If


End Sub

I substituted the troublesome report name in the app's form that deals with all the other reports that use a common class module and the same code in the OP works fine

Works great when functionality is launched from same form as the one for all the other reports. (as posted in #6)

[GraeagleBill]

I hate to bail out on a OP I started, but I can solve this issue by moving the functionality to another form. I have a lot to do and I have to move on. I commented out the troublesome code and I'll leave the tread open in case someone as the desire to continue with ideas.
Thanks,
Bill

[Minty]

I appreciate you are busy and have fixed this but my statement should have been "There is no filter or where clause in the open report command"
That is what I would term as a "dynamic filtered" report, not code in the report that does some adjusting.

[GraeagleBill]

Since I didn't post the report's Open Event code, you didn't see the RecordSource filtering determined based on a couple of the app's global variables. Anyway, at the time I saw your post, among other things I tried was to temporarily create a special RecordSource query for the report that reflected the filtering otherwise determined dynamically and attempted to again execute the OutputTo. I tried that both with and without a DoCmd.OpenReport occurring first but the error persisted.
Thanks for your follow-on thoughts,
Bill