Controls on a Report

[OldBirdman]

. . . apply only to forms and controls on a form, not controls on a report.

How do I put controls on a Report. Any attempt to do so has the 'Event' tab of the properties as blank.

If I can't have an event, it isn't a command button. It is a picture of a command button.

[maxamis4]

First you have to understand that reports are not forms. You can't just tell a report to run a function and it does it for you. A report is the output of something you created (obviously), but more importantly the report by the time you create is pretty much compilied. In reports however you still have event handlers like, On Open, On Load, and couple more I can't think of right now. Those are your event handlers if you still want to add any sort of constraint or code generated formatting. A good example of this is using a On Open event to prompt you for a date range using a form. This will allow and limit the report to a specific date criteria.

http://www.mvps.org/access/reports/index.html

Give that a look and see if it helps.

[OldBirdman]

For years, I've seen the quote

. . . apply only to forms and controls on a form, not controls on a report.

in Access Help. I found it again today on KeyDown, KeyUp Events. I was just curious why Help would continually tell me what I could and could not do with controls on a Report, if I couldn't put controls on a Report anyway.
I do understand that events can occur for the Report, Open, Close, Activate, Page, NoData. When I am free of development, and don't have the Access Toolbars/Menus, how do I switch from Preview to Print?

A good example of this is using a On Open event to prompt you for a date range using a form. This will allow and limit the report to a specific date criteria.

My personal programming style is to have ALL options covered before getting to the Report Load Event, and not to have a button that says "Print", that doesn't print, but asks for more information.

[ADezii]

@OldBirdman

1. The following code demos how you can dynamically create Controls on a Report:
   

   Dim rpt As Report
   Dim ctlLabel As Control
   Dim ctlText As Control
   Dim intDataX As Integer
   Dim intDataY As Integer
   Dim intLabelX As Integer
   Dim intLabelY As Integer
    
   DoCmd.OpenReport "Report1", acViewDesign
    
   Set rpt = Reports("Report1")
    
   'Position Text Box and associated Label
   intLabelX = 100
   intLabelY = 100
   intDataX = 1000
   intDataY = 100
    
   'Create 'Bound' ([LastName]) Default-size text box in Detail Section.
   Set ctlText = CreateReportControl(rpt.Name, acTextBox, acDetail, "", _
                                     "LastName", intDataX, intDataY)
    
   'Create child label control for the Text Box.
   Set ctlLabel = CreateReportControl(rpt.Name, acLabel, acDetail, _
                  ctlText.Name, "NewLabel", intLabelX, intLabelY)
    
   DoCmd.Close acReport, "Report1", acSaveYes

2. You can create Event Procedures in a Form, Report, Controls on a Report, Form and Report Sections, but to the best of my knowledge you cannot create Event Procedures for Controls on a Report itself. To create Event Procedures, use the CreateEventProc() Method. This Method if easy enough to use and is documented in the Help Files.

[missinglinq]

I was just curious why Help would continually tell me what I could and could not do with controls on a Report, if I couldn't put controls on a Report anyway.

Who said you couldn't put Controls on Report? Of course you can put Controls on Reports. The Controls simply don't have the same Events available! You can't enter or exit a Textbox on a Report, obviously, or click on a Radio Button, or do a lot of thing you can on a Form.

Amazingly, I understand that in version 2007 you can place a Command Button that does have a OnClick Event! Most curious!

Linq ;0)>

[mshmyob]

You are quite correct about being able to put command buttons and OnClick even mouse events, focus events, etc in AC2007. I have used it multiple times now and it works just fine.

cheers,

@missinglinq

[OldBirdman]

Somehow, I had it in my head that controls, at least when talked about in Help in conjunction with KeyDown, Click, etc. were things that could be manipulated.

My bad. Of course controls are all the textboxes on the report. And of course they cannot have events associated with them. I just had my mind set funny, and I needed the kink of kick you gave me. Thank you for your time.