database design

  • Thread starter Thread starter Kevin Kleinholter
  • Start date Start date
K

Kevin Kleinholter

Everytime I select a value in a combo box, I need certain check boxes to
appear on that form. The combo box is ClientNum and the check boxes
that need to appear are subClients. Example: When Client1 is selected
in the combo box, Client1a, Client1b, and Client1c need to appear on the
form as check boxes. All of this is done for a certain ProjectNumber.
If project 1 has Client1 selected, when I switch to Project2, it needs
to have its clients selected, not the same ones as project1.

The reason that the check boxes are selected is that they are the ones
who are going to be involved in the project. When Project1 has been
selected, Project1a, Project1b, and Project1c need to appear already
checked and then the user will deselect the clients that don't apply.

My question is: How can I design this and get everything to work
properly? I have tried many different ways, but my main problem is that
I cannot keep the clients to their ProjectNumber.

If this is not too confusing, I would appreciate the help!

Thanks

K
 
Everytime I select a value in a combo box, I need certain check boxes to
appear on that form. The combo box is ClientNum and the check boxes
that need to appear are subClients. Example: When Client1 is selected
in the combo box, Client1a, Client1b, and Client1c need to appear on the
form as check boxes. All of this is done for a certain ProjectNumber.
If project 1 has Client1 selected, when I switch to Project2, it needs
to have its clients selected, not the same ones as project1.
Click to expand...

Do you have *FIELDS* for Client1a and Client1b and so on? Or do you
have two Tables in a one-to-many relationship? What's the structure of
your Tables?

Don't worry about the Forms - windows which let you manipulate the
data in your Tables - until you have your Table structures correct;
I'm guessing that at present you do not!
 
Right now I have one table that has, amoung other information, a Clients
field and a Groups field. Not all clients are associated with a group,
though. For the ones that are not associated with a group, the group field
is left blank. For all others, the Group field is filled with the group that
they are associated with.

I am not sure how to save the clients that have been selected for each
ProjectID.

Thanks for the help,

K
 
Right now I have one table that has, amoung other information, a Clients
field and a Groups field. Not all clients are associated with a group,
though. For the ones that are not associated with a group, the group field
is left blank. For all others, the Group field is filled with the group that
they are associated with.
Click to expand...

This design will allow a client to belong to either zero or one Group;
it will prohibit membership in more than one group. Is that what you
want?
I am not sure how to save the clients that have been selected for each
ProjectID.
Click to expand...

I presume that each Client can be associated with more than one
Project, and that each Project will involve one or more Clients -
right?

If so you have a many to many relationship; the way such relationships
are handled in any relational database is by adding a new table *for
the relationship itself*. This table would have fields for the
ClientID and the ProjectID; you'ld add a record to the table for each
unique client-project pairing.
 
Each client will have only one Master Client(group) associated with it. For
example, Client1a will only be associated with Client1, no one else.

Each project will have only one Master Client associated with it. For example,
Project1 will have Client1, which then is subdivided into Client1a, Client1b,
Client1c.

Project2 will have Client2, which is then subdivided into Client4, which is then
subdivided into Client4a, Client4b, Client4c,etc.

Project3 will have Client1 as well, which could have different or the same
subclients.
Project3 could have Client1a, Client1b, Client1e, Client1f.

Each Master Client can have many different subclients, but not all Projects will
use all the subclients. That is what I need the check boxes for. If Master
Client1 is selected, I would like all of its Subclients to appear (e.g. Client1a -
Client1g), and then let the user select who will be involved with that particular
project.

Also, not all Master Clients have subclients associated with them.

I hope that I am making this clearer. I really appreciate the help.

Thanks,

K
 
Each client will have only one Master Client(group) associated with it. For
example, Client1a will only be associated with Client1, no one else.

Each project will have only one Master Client associated with it. For example,
Project1 will have Client1, which then is subdivided into Client1a, Client1b,
Client1c.

Project2 will have Client2, which is then subdivided into Client4, which is then
subdivided into Client4a, Client4b, Client4c,etc.

Project3 will have Client1 as well, which could have different or the same
subclients.
Project3 could have Client1a, Client1b, Client1e, Client1f.

Each Master Client can have many different subclients, but not all Projects will
use all the subclients. That is what I need the check boxes for. If Master
Client1 is selected, I would like all of its Subclients to appear (e.g. Client1a -
Client1g), and then let the user select who will be involved with that particular
project.
Click to expand...

I'm not visualizing how your tables are structured! Do you have
separate FIELDS for Client1a, or a Self Join query between the tables,
or what?

Please post the relevant fields of the table definitions, and how the
tables are related. I can sort of see the business model here but I'm
not at all sure I understand your data model!
 
Back
Top