From: SamMexico via AccessMonster.com on
Hi everyone, this may or may not be possible but I'll ask the question anyway.
..

I have a form with two butttons; each opening a different report. 'Report 1'
button and 'Report 2' button.

I also have another form that displays a drop down list where half of the
list relates to 'Report 1' and the other half to 'Report 2'. Is it possible
to make one button inactive if the criteria in the drop down list have not
been selected in the other form?

Thanks for any input you may be able to give me,

Sam

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/201006/1

From: Marshall Barton on
SamMexico via AccessMonster.com wrote:
>I have a form with two butttons; each opening a different report. 'Report 1'
>button and 'Report 2' button.
>
>I also have another form that displays a drop down list where half of the
>list relates to 'Report 1' and the other half to 'Report 2'. Is it possible
>to make one button inactive if the criteria in the drop down list have not
>been selected in the other form?


It probably is possible.

The details depend on which form is open when the button or
combo box is used and, assuming the combo box selection is
made before a button is used, how the items in the combo box
are identified as related to report1 or report2.

--
Marsh
MVP [MS Access]
From: nrgins via AccessMonster.com on
Just use the dropdown's AfterUpdate event to enable/disable the buttons based
on the user's selection.


SamMexico wrote:
>Hi everyone, this may or may not be possible but I'll ask the question anyway.
>..
>
>I have a form with two butttons; each opening a different report. 'Report 1'
>button and 'Report 2' button.
>
>I also have another form that displays a drop down list where half of the
>list relates to 'Report 1' and the other half to 'Report 2'. Is it possible
>to make one button inactive if the criteria in the drop down list have not
>been selected in the other form?
>
>Thanks for any input you may be able to give me,
>
>Sam

--
Message posted via http://www.accessmonster.com