I was hoping someone out there could help me out.
I'm using CR7 in a VB5 application to generate a report based on records in a MS Access database but only populates those based on a specific date range. CR7 has a neat feature that let's you specify specific parameter values (for example, date type) to restrict what is displayed. However, when I run the app and click the print command button to launch the date range window (which includes start and end date), included in this window is a selection for upper/lower bound as well as a check box if I want the date range to be inclusive or exclusive. I would like to eliminate these extra features when I run my program in production. I works well enough with these extras on but if a user inadvertantly checks one of these boxes and presses the print command, he/she'll get an automation error. I would like to prevent this possibility from occurring by eliminating this in the first place. Also, how do I prevent an automation error if the user presses the 'Cancel' button instead of the 'OK' button. I know this was a mouthful but any help with this would be greatly appreciated.
I'm using CR7 in a VB5 application to generate a report based on records in a MS Access database but only populates those based on a specific date range. CR7 has a neat feature that let's you specify specific parameter values (for example, date type) to restrict what is displayed. However, when I run the app and click the print command button to launch the date range window (which includes start and end date), included in this window is a selection for upper/lower bound as well as a check box if I want the date range to be inclusive or exclusive. I would like to eliminate these extra features when I run my program in production. I works well enough with these extras on but if a user inadvertantly checks one of these boxes and presses the print command, he/she'll get an automation error. I would like to prevent this possibility from occurring by eliminating this in the first place. Also, how do I prevent an automation error if the user presses the 'Cancel' button instead of the 'OK' button. I know this was a mouthful but any help with this would be greatly appreciated.