Re: Users want Check Boxes for entry

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Allen Browne (AllenBrowne_at_SeeSig.Invalid)
Date: 01/20/05 

Date: Thu, 20 Jan 2005 22:06:13 +0800

If you use a numeric primary key for your Application_rejected_reasons
table, then you could interface the foreign key field with an option group.
The group lists all the reasons, and the field stores the number of the
seleted box.

The major drawback of this interface is that when new reasons are added
later, you have to redesign the form so the option group contains the extra
boxes. 

-- 
Allen Browne - Microsoft MVP.  Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Melvis" <Melvis@discussions.microsoft.com> wrote in message
news:D884E7E8-E30E-4659-AA86-72672C466354@microsoft.com...
> Hi,
>
> I am in the process of making a database to track application rejections 
> for
> a colleague. What happens is people apply for tags, and they need a way to
> track why the rejections were rejected. They do not track the applications
> that go through.
>
> The table structure seems easy to me, with an Aapplication table, a
> Reason_for_rejection table, and an Application_rejected_reasons table.
> Normally for this type of table schema, I would use a subform for them to
> choose the reasons. But what the supervisor is asking for is like a paper
> form with check boxes for each reason. She thinks this will be faster and
> more efficient for her employees when they are entering the rejections 
> into
> the database.
>
> What I am wondering is if there is any way to accomplish waht she wants
> without pulling out all my hair. Could I use an array of check boxes? If 
> so,
> how? This way I could at least loop through the check boxes to see which 
> ones
> are checked rather than writing code for each one. Also, there is the
> possibility that the reasons could change in the future, so I would need 
> the
> ability to populate the labels from the Reasons table. Man, this sounds
> freaky!
>
> Any help you could possibly give me on this would be greatly appreciated.
> Thanks...
> ~MATT

Relevant Pages

  • Users want Check Boxes for entry
    ... track why the rejections were rejected. ... the database. ... Could I use an array of check boxes? ... possibility that the reasons could change in the future, ...
    (microsoft.public.access.forms)
  • Re: Users want Check Boxes for entry
    ... and then loop through the checkboxes ... >> existing data if the reasons are changed, ... >>>>> track why the rejections were rejected. ... >>>>> form with check boxes for each reason. ...
    (microsoft.public.access.forms)
  • Re: Users want Check Boxes for entry
    ... Given the difficulty in adding new reasons, ... you have to redesign the form so the option group contains the ... >>> track why the rejections were rejected. ... >>> form with check boxes for each reason. ...
    (microsoft.public.access.forms)
  • Re: Users want Check Boxes for entry
    ... couple reasons without programming, but can definitely CHANGE the reasons at ... then you could interface the foreign key field with an option group. ... >> track why the rejections were rejected. ... >> form with check boxes for each reason. ...
    (microsoft.public.access.forms)
  • Re: Users want Check Boxes for entry
    ... Couldn't he dynamically add those checkboxes to the form? ... change on the adding/deleting of reasons in that table. ... simply create an Option Group control. ... >> track why the rejections were rejected. ...
    (microsoft.public.access.forms)