Sturts said:
I've been trying to figure this out for over a week now. I'm attempting to make a form where there is an option group with 5 options (I have that completed. My problem is that I not only need the checkboxes but two textboxes binded to the "fail" option. Within the form I need it so that if the tech clicks "fail" he can type why it failed and also the parts required to fix the problem. I can't seem to find a way to do this without putting "why failed" and "parts required" into my question table, even then I would have a problem with my query as I need to be able to query what failed and why then put that into a report without all the other options. Any help is much appreciated.
Thanks in advance
Sean Sturts (USMC)
Well, it's hard to interpret what's going on here, but I'm going to take a stab at it.
You have a table, maybe called something like "tblTroubleTicket" where techs keep track of the work they are doing. You have a form for the trouble ticket table, where the tech puts in all the data about what he did to fix the problem. Everything works fine unless the tech can't fix it and needs to order parts.
So, since it seems to me like each trouble ticket can fail multiple times, I would make a new table called "tblFailures" and put these columns in it:
tblFailures
FailID Autonumber
TroubleTicketID Long
WhyFail Text
PartsOrdered Text
----------------
note: TroubleTicketID should be named the same as the primary key in your main table, IMO
Make a new form (frmFail maybe), as small as you can, with two text boxes. Set the record source for the form as "SELECT * FROM tblFailures;". Set the data control on the two text boxes to be WhyFail and PartsOrdered. Save and close the form, then open your main trouble ticket form. Add a subform control to it that is just a little bit larger than frmFail. Set the properties on it to like this
Source Object: frmFail
Link Master Field: TroubleTicketID
Link Child Field: TroubleTicketID
Visible: no
(you've got to set the source object before the link properties)
Then, on the check box that indicates failure, bind the click option to toggle the visible property on the subform. So when the user clicks "fail" this subform will pop up, and many different failures can be entered.
You can also base other forms or reports solely on the failures.
This is just what I would do. I've grown fond of subforms, but I'm not sure if they're considered to be good Access programming practice. Of course, if each trouble ticket can ever only fail once, then there's little point in making a whole new table.
Normalization??? hay wuts that
