Mr. Browne,
I need to revisit a few things here if you don't mind. I am going to
crosspost to Database Design as well.
Allen Browne Wrote:
"There are multiple ways to interface SuspectID and PetitionerID without
having to show the AutoNumber values. One way is to use a combo box, where
the RowSource is something like this:
SELECT PetitionerID, Surname & ", " + Firstname AS PetitionerName
FROM tblPetitioner
ORDER BY Surname, FirstName, PetitionerID;
Then set the first column to zero-width, so it stores the hidden
PetitionerID value, but displays the name:
Column Count 2
Column Widths 0
Bound Column 1 "
I now understand about the combo boxes you mentioned for PetitionerID. My
first question is this: Do I need to make a separate table tblPetitioner? If
so, I assume it would need to have PetitionerID (PK Autonumber), FirstName,
LastName, PhoneNumber, Department ?
Assuming that table structure, Next question is: Do I need a separate form
to enter the Petitioner info? Would a sub-subform or subform be better?
Now, assuming it is set up this way, is it then correct to place a combo box
cboPetitioner bound to the PetitionerID PK field that does the query you gave
me earlier to combine the First and Last Name on the sfrmBolo subform? The
question is then, do I put the query "code" in the rowsource space on the
combo options, and how do I make this combo a drop-down list? Let me
clarify...if the petitioner does not exist in the list in the combo, I want
the add petitioner form to pop-up, so a new petitioner can be added. I do not
want the user to be able to just type a garbage name in the combo, since
first and last names are in separate fields. I want to prevent user error and
confusion as much as possible.
Last thing is I assume after setting it up this way, I would merely need to
do a dlookup to pull the petitioner phone and department into the sfrmBolo
subform?
Am I on the right track?
Thanks again for your help,
Derek