Hi listers,
Help, please. My brain is a puny thing.
I have a "Projects" database that includes these tables and relationships, among others:
tblProjects - pkeyProjectID
fkeyClientID
tblClients - pkeyClientID
txtClient
fkeyGroupID
tblGroup - pkeyGroupID
txtGroup
In prose: each Project (i.e., "Map of penguin sites") is completed at the request of a client ("Mike Smith") who belongs to a more generalized group ("Science", "Logistics"). I currently have ~100 individual clients aggregated into 4 main groups.
On the main form "frmProjectEntry" I have combo boxes cboGroup (unbound) and cboClient (bound). After the user chooses the Group, the cboClient box shows only those clients that belong to that particular Group.
That part works wonderfully. What *doesn't* work is that since cboGroup is unbound, no group is displayed when I go back through the data I've entered previously. That makes sense, since the box is unbound, but it's annoying.
Making cboGroup bound to the underlying table (by inserting an "fkeyGroupID" into tblProjects) seems to be poor database design, however.
Any ideas?
Thanks very much in advance...
J
Help, please. My brain is a puny thing.
I have a "Projects" database that includes these tables and relationships, among others:
tblProjects - pkeyProjectID
fkeyClientID
tblClients - pkeyClientID
txtClient
fkeyGroupID
tblGroup - pkeyGroupID
txtGroup
In prose: each Project (i.e., "Map of penguin sites") is completed at the request of a client ("Mike Smith") who belongs to a more generalized group ("Science", "Logistics"). I currently have ~100 individual clients aggregated into 4 main groups.
On the main form "frmProjectEntry" I have combo boxes cboGroup (unbound) and cboClient (bound). After the user chooses the Group, the cboClient box shows only those clients that belong to that particular Group.
That part works wonderfully. What *doesn't* work is that since cboGroup is unbound, no group is displayed when I go back through the data I've entered previously. That makes sense, since the box is unbound, but it's annoying.
Making cboGroup bound to the underlying table (by inserting an "fkeyGroupID" into tblProjects) seems to be poor database design, however.
Any ideas?
Thanks very much in advance...
J