difficulty with combo box "limit to list"; selecting multiple choices

[sturose2000]

Two questions that may be related:
I'm using Access 2002 to store information gathered from interviews. Among
other things, I have a table for Organizations, a table for Contacts, and a
table for PeopleTypes.

Suppose I'm entering a record for a new Contact.

1. I have a combo box to select which Organization the Contact is associated
with. The field Contacts.Organization is bound by: SELECT
Organizations.OrgID, Organizations.[Organization Name] FROM Organizations;
I've tried to set the Limit To List = No, but since OrgID is hidden I cannot
do that. Ideally, if I enter an Organization that is not in the
Organizations table, can Access create a new entry in Organizations (giving
it the Autonumber OrgID and filling in OrganizationName)?

2. I have a combo box to select which Category the Contact is (e.g. Category
= "Student," "Faculty," "Administrator," etc.) Again, the box is bound by
SELECT PeopleTypes.[PeopleType ID], PeopleTypes.[PeopleType Label] FROM
PeopleTypes; Is there a way to let a single Contact select multiple
PeopleTypes (e.g. John Doe is both Student and Employee) or do I need to use
separate fields?

Thanks in advance,
Stu

(e-mail address removed) (remove _NOSPAM to reply)

 

[Guest]

For your question #1 you might want to look up Not In List events.

Also, I don't understand how a combo is bound by SQL. Usually, the SQL is the row source and the selection in the combo is bound to a field in the table.

By the way, this post is dated earlier than the one where you posted a link to the db you are working on. Does that db have the problems you're describing here?

 

[sturose2000]

Also, I don't understand how a combo is bound by SQL. Usually, the SQL is

the row source and the selection in the combo is bound to a field in the
table.
It's not bound by SQL. In the few days between this post and my more recent
one, I learned the correct terminology and better understood the
relationships between different parts of the db.

By the way, this post is dated earlier than the one where you posted a

link to the db you are working on. Does that db have the problems you're
describing here?
It did. It's the same one. But now it's a moot point: since I've actually
started filling in records, it turns out that in reality I didn't even need
this feature!