Arthur Fuller
fuller.artful at gmail.com
Sun Apr 8 11:39:21 CDT 2012
I would move the buttons off the report itself an onto a pop-up dialog with either option buttons or checkboxes (the latter allowing more than one choice to be selected). Then you could pass in the selected value and use it in the Report_Open event to set the desired color. On Sun, Apr 8, 2012 at 11:41 AM, Brad Marks <BradM at blackforestltd.com>wrote: > Charlotte, > > Thanks for your ideas. I have not yet found time to experiment with > custom toolbars or ribbons. I hope to do so down the road. > > I am trying to make things as easy as possible for the users. > > I do not know how to move the focus off of a button. That sounds like a > good idea. Could you explain how to do this. > > Thanks, > Brad > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com on behalf of Charlotte Foust > Sent: Sun 4/8/2012 10:28 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] How to Prevent a button from being printed on > areport. > > Brad, why not just create a custom toolbar or ribbon available to the user > only in report view instead? It would allow you to do the same thing > without having to fight the buttons. Alternatively, use code to move the > focus off the button in its on click event so that it no longer has the > focus and see if that corrects the problem. > > Charlotte Foust > > On Sun, Apr 8, 2012 at 8:08 AM, Brad Marks <BradM at blackforestltd.com> > wrote: > > > Rocky, > > > > Thanks for the help. > > > > I didn't fully explain things. > > > > The report is being opened in "Report View" (Access 2007/2010). > > > > The buttons that control the color of the headings are pushed after the > > report is already opened (the buttons are actually on the report itself). > > > > They enable the users to change colors "on the fly", once they see the > > report on the screen. They need to look at the report before they decide > > to print it or not. > > > > Brad > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com on behalf of Rocky Smolin > > Sent: Sun 4/8/2012 10:00 AM > > To: 'Access Developers discussion and problem solving' > > Subject: Re: [AccessD] How to Prevent a button from being printed on > > areport. > > > > In the open event of the report can you just see which button is pushed > > (maybe make it an option frame - then you'd have a value of 1, 2, or 3). > > Then change the color of the heading or border or some other control on > the > > report to the appropriate color? > > > > Rocky > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks > > Sent: Sunday, April 08, 2012 7:40 AM > > To: Access Developers discussion and problem solving > > Subject: [AccessD] How to Prevent a button from being printed on a > report. > > > > All, > > > > We have an Access Report that has three buttons near the top of the > report. > > > > The purpose of these buttons is to change the color of the report header > > section to green, blue, or yellow. > > > > The different colors are used to differentiate between the "Accounting > > Copy", the "File Copy" and the "Production Copy". > > > > This approach is being implemented to replace an older method of using > > different colored paper. > > > > The users love this new approach because they can simply print the report > > on > > plain white paper and no longer need to load different colored paper into > > their printers. > > > > We are seeing one small glitch that I would like to better understand and > > to > > resolve. > > > > The "Display When" property is set to "Screen Only" for the three > buttons. > > > > However, if a user clicks on one of the buttons and then prints the > report > > (Via the round Office Button in the upper left corner of the screen) the > > color button that was pushed is printed on the report. > > > > We have found that if the user clicks on another place on the report > > (outside of the color button), then the button is not printed on the > > report. > > > > I believe that this is related to the button "having focus", but I can't > > understand why it would still have focus after the Office button is > pushed > > and "Print" is selected. > > > > One more little tidbit. Development is currently being done with Access > > 2007, and deployment is on Access 2010. I am not sure if this makes a > > difference or not. > > > > Thanks, > > Brad > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > > > > > Website: http://www.databaseadvisors.com > > > > > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > > > > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > > > > > Website: http://www.databaseadvisors.com > > > > > > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- Arthur Cell: 647.710.1314 Prediction is difficult, especially of the future. -- Niels Bohr