Default View Print Preview

[dmschenk]

How can I make Print Preview the default view for a report straight out of the switchboard? Currently when you click to open a report it opens in report view and you have to right click to select Print view. In design view my report says the default view is Print Preview but that is only for opening it directly. When you select from the switchboard menu that option doesn't exist. Is there a way to get the print preview to be the default view?

Thanks
Dave

 

[Freshman]

Maybe set up a Macro to open the report in pre-view and then point to the macro from the SWB.

PS: I hate Access' build-in SWB and always create my own with code at the back.

 

[ghudson]

I never liked the restrictions of the switchboard so I make everything from scratch in my forms.

I give my users the choice to either preview or print the report when they select the report form a combo box listings the available reports from that form.

        If MsgBox("Do you want print or preview the ''" & cboPrintReports & "'' report?" & vbCrLf & vbCrLf & "Click the Yes button to print the selected report." & vbCrLf & "Click the No button to preview the selected report.", vbQuestion + vbYesNo, "Print Or Preview Selected Report") = vbYes Then
            DoCmd.OpenReport sReportName, acViewNormal
            MsgBox "The selected report has been sent to your default printer.", vbInformation, "Printed " & cboPrintReports & " Report"
        Else
            DoCmd.OpenReport sReportName, acViewPreview
        End If

 

[Clownfish1980m]

ghudson, I like the idea of a choice of either preview or print. What event property do you put the coding (i.e. onOpen, onUpdate) ? Thanks Ken

 

[gemma-the-husky]

except that doing that involves an extra key press each time, which I would definitely find very irritating. So i would rather have a button to select the active print mode (eg print/preview/pdf/email even)

I take it we are considering A2007 or A2010 switchboards. I still use a (modified) version of earlier switchboards, which use code, rather than macros. (I report errors differently, and have extra startup functions like checking screen resolution, and checking locale settings. I also have user logins which affect the menu options which get displayed)

In A2003 and earlier switchboards, it is easy to modify the code in the HandleButtonclick event, to do something different with any menu option. It is probably the same in A2007/A2010, but I know they use macros rather than code, so it is possibly a little different.