Yes / No boxes in a report question

[Nurse Matthew]

I have a report that is a flowsheet of patient behaviors in a hospital
classroom setting.
There are around 60 checkboxes, covering a wide variety of observable
behaviors. I have a great form set up, that can make data entry a breeze, and
a pretty good report... but...
I want the report to only show the items that were checked in the form.
Currently it shows everything, checked or not. This would be too confusing to
make good reading material.
Examples for a section regarding appearance, I have the following boxes:
"Alert"
"Attentive"
"Drowsy"
"Neat / Clean"
"Unkempt"
"Disengaged"
etc.
If a patient was Alert, Attentive, Neat / Clean, that's all I want that
section to show (in my report).

Can anyone help?
Matthew

 

[Jake]

I would try something like this, a single text box with a "Controll Source" of:

=iif([Alert_Check], "Alert ","") & iif([Attentive_Check], "Attentive ","") &
iif([Drowsy_Check], "Drowsy ","") & iif([NeatClean_Check], "Neat / Clean
","") & iif([Unkempt_Check], "Unkempt ","") & iif([Disengaged_Check],
"Disengaged ","")

Jacob

 

[Duane Hookom]

I think you have a serious issue with normalization. My preference for a
table structure would use a separate record for each behaviour. Normalized
tables would make your report a breeze.

Your form might be great but a form shouldn't drive your data storage.

--
Duane Hookom
Microsoft Access MVP

I would try something like this, a single text box with a "Controll Source" of:

=iif([Alert_Check], "Alert ","") & iif([Attentive_Check], "Attentive ","") &
iif([Drowsy_Check], "Drowsy ","") & iif([NeatClean_Check], "Neat / Clean
","") & iif([Unkempt_Check], "Unkempt ","") & iif([Disengaged_Check],
"Disengaged ","")

Jacob

I have a report that is a flowsheet of patient behaviors in a hospital
classroom setting.
There are around 60 checkboxes, covering a wide variety of observable
behaviors. I have a great form set up, that can make data entry a breeze, and
a pretty good report... but...
I want the report to only show the items that were checked in the form.
Currently it shows everything, checked or not. This would be too confusing to
make good reading material.
Examples for a section regarding appearance, I have the following boxes:
"Alert"
"Attentive"
"Drowsy"
"Neat / Clean"
"Unkempt"
"Disengaged"
etc.
If a patient was Alert, Attentive, Neat / Clean, that's all I want that
section to show (in my report).

Can anyone help?
Matthew

 

[Nurse Matthew]

Thank you, thank you, thank you!

I would try something like this, a single text box with a "Controll Source" of:

=iif([Alert_Check], "Alert ","") & iif([Attentive_Check], "Attentive ","") &
iif([Drowsy_Check], "Drowsy ","") & iif([NeatClean_Check], "Neat / Clean
","") & iif([Unkempt_Check], "Unkempt ","") & iif([Disengaged_Check],
"Disengaged ","")

Jacob

I have a report that is a flowsheet of patient behaviors in a hospital
classroom setting.
There are around 60 checkboxes, covering a wide variety of observable
behaviors. I have a great form set up, that can make data entry a breeze, and
a pretty good report... but...
I want the report to only show the items that were checked in the form.
Currently it shows everything, checked or not. This would be too confusing to
make good reading material.
Examples for a section regarding appearance, I have the following boxes:
"Alert"
"Attentive"
"Drowsy"
"Neat / Clean"
"Unkempt"
"Disengaged"
etc.
If a patient was Alert, Attentive, Neat / Clean, that's all I want that
section to show (in my report).

Can anyone help?
Matthew

 

[Nurse Matthew]

I'm a bit flummoxed...
I'm not quite smart enough for this. Do you have an example?

I'm all for making things simpler, and I'm still early enough in the process
to re-start.
Matthew

I think you have a serious issue with normalization. My preference for a
table structure would use a separate record for each behaviour. Normalized
tables would make your report a breeze.

Your form might be great but a form shouldn't drive your data storage.

--
Duane Hookom
Microsoft Access MVP

I would try something like this, a single text box with a "Controll Source" of:

=iif([Alert_Check], "Alert ","") & iif([Attentive_Check], "Attentive ","") &
iif([Drowsy_Check], "Drowsy ","") & iif([NeatClean_Check], "Neat / Clean
","") & iif([Unkempt_Check], "Unkempt ","") & iif([Disengaged_Check],
"Disengaged ","")

Jacob

I have a report that is a flowsheet of patient behaviors in a hospital
classroom setting.
There are around 60 checkboxes, covering a wide variety of observable
behaviors. I have a great form set up, that can make data entry a breeze, and
a pretty good report... but...
I want the report to only show the items that were checked in the form.
Currently it shows everything, checked or not. This would be too confusing to
make good reading material.
Examples for a section regarding appearance, I have the following boxes:
"Alert"
"Attentive"
"Drowsy"
"Neat / Clean"
"Unkempt"
"Disengaged"
etc.
If a patient was Alert, Attentive, Neat / Clean, that's all I want that
section to show (in my report).

Can anyone help?
Matthew

 

[Duane Hookom]

My suggestion would follow the basic structure of the At Your Survey or
Employee Evaluation samples at
http://www.rogersaccesslibrary.com/forum/forum_topics.asp?FID=4&SID=e14z345z542zzfaz3z85bc631z8a91ff.

Adding more "observable behaviours" should result in adding records to
tables, not fields and controls to forms and reports and queries.

--
Duane Hookom
Microsoft Access MVP

I'm a bit flummoxed...
I'm not quite smart enough for this. Do you have an example?

I'm all for making things simpler, and I'm still early enough in the process
to re-start.
Matthew

I think you have a serious issue with normalization. My preference for a
table structure would use a separate record for each behaviour. Normalized
tables would make your report a breeze.

Your form might be great but a form shouldn't drive your data storage.

--
Duane Hookom
Microsoft Access MVP

I would try something like this, a single text box with a "Controll Source" of:

=iif([Alert_Check], "Alert ","") & iif([Attentive_Check], "Attentive ","") &
iif([Drowsy_Check], "Drowsy ","") & iif([NeatClean_Check], "Neat / Clean
","") & iif([Unkempt_Check], "Unkempt ","") & iif([Disengaged_Check],
"Disengaged ","")

Jacob

:

I have a report that is a flowsheet of patient behaviors in a hospital
classroom setting.
There are around 60 checkboxes, covering a wide variety of observable
behaviors. I have a great form set up, that can make data entry a breeze, and
a pretty good report... but...
I want the report to only show the items that were checked in the form.
Currently it shows everything, checked or not. This would be too confusing to
make good reading material.
Examples for a section regarding appearance, I have the following boxes:
"Alert"
"Attentive"
"Drowsy"
"Neat / Clean"
"Unkempt"
"Disengaged"
etc.
If a patient was Alert, Attentive, Neat / Clean, that's all I want that
section to show (in my report).

Can anyone help?
Matthew

 

[Nurse Matthew]

Thank you.
With so many Yes/No fields, it's very time consuming. Adding or Deleting
behaviors will be a nightmare in its current shape.

NM

My suggestion would follow the basic structure of the At Your Survey or
Employee Evaluation samples at
http://www.rogersaccesslibrary.com/forum/forum_topics.asp?FID=4&SID=e14z345z542zzfaz3z85bc631z8a91ff.

Adding more "observable behaviours" should result in adding records to
tables, not fields and controls to forms and reports and queries.

--
Duane Hookom
Microsoft Access MVP

I'm a bit flummoxed...
I'm not quite smart enough for this. Do you have an example?

I'm all for making things simpler, and I'm still early enough in the process
to re-start.
Matthew

I think you have a serious issue with normalization. My preference for a
table structure would use a separate record for each behaviour. Normalized
tables would make your report a breeze.

Your form might be great but a form shouldn't drive your data storage.

--
Duane Hookom
Microsoft Access MVP


:

I would try something like this, a single text box with a "Controll Source" of:

=iif([Alert_Check], "Alert ","") & iif([Attentive_Check], "Attentive ","") &
iif([Drowsy_Check], "Drowsy ","") & iif([NeatClean_Check], "Neat / Clean
","") & iif([Unkempt_Check], "Unkempt ","") & iif([Disengaged_Check],
"Disengaged ","")

Jacob

:

I have a report that is a flowsheet of patient behaviors in a hospital
classroom setting.
There are around 60 checkboxes, covering a wide variety of observable
behaviors. I have a great form set up, that can make data entry a breeze, and
a pretty good report... but...
I want the report to only show the items that were checked in the form.
Currently it shows everything, checked or not. This would be too confusing to
make good reading material.
Examples for a section regarding appearance, I have the following boxes:
"Alert"
"Attentive"
"Drowsy"
"Neat / Clean"
"Unkempt"
"Disengaged"
etc.
If a patient was Alert, Attentive, Neat / Clean, that's all I want that
section to show (in my report).

Can anyone help?
Matthew

 

[Duane Hookom]

The normalized solution makes adding yes/no values as simple as adding a
record to a table. Some developers prefer to keep the "spreadsheet" type
design since they find it easier. I much prefer the small advance effort to
build the tables normalized.

--
Duane Hookom
Microsoft Access MVP

Thank you.
With so many Yes/No fields, it's very time consuming. Adding or Deleting
behaviors will be a nightmare in its current shape.

NM

My suggestion would follow the basic structure of the At Your Survey or
Employee Evaluation samples at
http://www.rogersaccesslibrary.com/forum/forum_topics.asp?FID=4&SID=e14z345z542zzfaz3z85bc631z8a91ff.

Adding more "observable behaviours" should result in adding records to
tables, not fields and controls to forms and reports and queries.

--
Duane Hookom
Microsoft Access MVP

I'm a bit flummoxed...
I'm not quite smart enough for this. Do you have an example?

I'm all for making things simpler, and I'm still early enough in the process
to re-start.
Matthew

:

I think you have a serious issue with normalization. My preference for a
table structure would use a separate record for each behaviour. Normalized
tables would make your report a breeze.

Your form might be great but a form shouldn't drive your data storage.

--
Duane Hookom
Microsoft Access MVP


:

I would try something like this, a single text box with a "Controll Source" of:

=iif([Alert_Check], "Alert ","") & iif([Attentive_Check], "Attentive ","") &
iif([Drowsy_Check], "Drowsy ","") & iif([NeatClean_Check], "Neat / Clean
","") & iif([Unkempt_Check], "Unkempt ","") & iif([Disengaged_Check],
"Disengaged ","")

Jacob

:

I have a report that is a flowsheet of patient behaviors in a hospital
classroom setting.
There are around 60 checkboxes, covering a wide variety of observable
behaviors. I have a great form set up, that can make data entry a breeze, and
a pretty good report... but...
I want the report to only show the items that were checked in the form.
Currently it shows everything, checked or not. This would be too confusing to
make good reading material.
Examples for a section regarding appearance, I have the following boxes:
"Alert"
"Attentive"
"Drowsy"
"Neat / Clean"
"Unkempt"
"Disengaged"
etc.
If a patient was Alert, Attentive, Neat / Clean, that's all I want that
section to show (in my report).

Can anyone help?
Matthew