Error warning for Combo Box if doesn't match Check Box on another Form

[kerrymct478]

I am new to VBA/Microsoft Access. I am trying to get an error message to pop up if someone select "yes" to something but left a check box for the same thing blank in a different form. These forms are connected. One form is identifying information for the patient, and the second one is clinical information. Any suggestions?

[NeoPa]

Hi Kerry. Have you considered removing the option for 'Yes' if the other CheckBox is not selected?

If this is practicable then it would certainly allow for a less clumsy interface. It can be done both ways, of course.

Either approach will require a clear understanding of how all the relevant items relate to each other. I suggest, if you're likely to need help accomplishing this task, that you make those relationships and requirements clear explicitly.

[hvsummer]

@Kerrymct478: welcome to bytes.com

I am new to VBA/Microsoft Access. I am trying to get an error message to pop up if someone select "yes" to something but left a check box for the same thing blank in a different form. These forms are connected. One form is identifying information for the patient, and the second one is clinical information. Any suggestions?

the first thing I have to tell you that you can't get value represent for "left a check box" from a different form.
When that "different form" closed, everything unload, even controls.value, even these forms are connected, only available when they 're form and subform (open together then that not problem).

to cheat this problem, you can temporary save checkbox.value in a field of tblTemp or in a collection, or even the class module (this method's too complex as we have to code a lot)==

if I was you, I would choose this:

1. bring those form together as form and subform.

2. using vba with collection or tblTemp to temporary save checkbox.value (that could be true or false)
then compare these value have to match (false-false, true-true or it'll msgbox("Error on Checkbox" & i, vbCritical,"Information don't match"))

and as NeoPa said, you should considering disable checkbox when the same checkbox on the innitial form did not check, that'll enable people to see the problem faster and lessen compare/checking handle.

[zmbd]

Let's see Kerrymct478's reply to Neopa before we start jumping in with suggestions here... this way we have less of a chance of steering K down the wrong path.

HVSummerthe first thing I have to tell you that you can't get value represent for "left a check box" from a different form.

This is only true if the form is closed.
One can certainly reference any value on any open form for any control including those found on subforms.

For example, to reference a textbox on another currently open form one can useForms![openformname]![txtTest].Text

However, what I've found all too often is that there is a fundamental, logical design flaw in the database/interface when this needs to be done.

HVSummer2. using vba with collection or tblTemp to temporary save checkbox.value (that could be true or false)

Due to the inherent bloat in Access, IMHO, Temporary tables in Access should be avoided at all costs or, if needed, used in a temporary back-end database

IN this case, I really do not see the need for the added complication for the temporary table.
One would be much better off using the underlying record-set of the first form to see if the record has been properly set, or the very most, the tempvars.collection if and only if this is the only way - such as with the navigation-control.

I re-iterate: Let's see OP's response to Neopa. He makes a very good suggestion for clearing up the interface, asks for much needed information to steer our new member towards an elegant and efficient solution, and we don't know the nature of the current forms! Additionally, we have no idea of the table structure or even which version of Access/Office OP is using!