|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I have a mainform which identifies a project. On a subform, I would like to
display a list of team members for that project displayed in data view. I
cannot keep the entire list accessible in the data view. If I enter a name,
it will be displayed. If i close the main form, and open it later, only a
blank new cell will be visible, and there is no way to scroll to view the
other names. Is there a way to do this? One contributing factor may be that
the table used as the basis for the subform contains the names of all team
members on all projects. Does this preclude the ability to see a dynamic list
of all the names of a particular project at a time?
|
|
Main forms / sub forms will display related data based on the primary key /
foreign key relationship. Your subform must contain the primary key from the
main form, then you can relate the subform to the main form.
Does this make sense to you?
One of the issues you will run into is that a person can be part of more
than one project. So not only do you have to list the project number, but
you have to attach the person to each project. Therefore, you will need a
third table.
Project table that contains only project info: Project Id, Start Date, End
Date etc.
Employee table: contains all the employees regardless on whether they work a
project.
Projects and Employee Details table: Primary Key from Project table, Primary
Key from Employee table, any other data that pertains to details of the
employee on the project.
In the latter table, this is where you will show multiple entries per
employee, with each project ID. I would set both primary keys as the
combined key for this table. This will prevent you from listing the same
individual to the same project id.
Use this latter table to connect to your mainform.
"Ryn5000" <Ryn5000[ at ]discussions.microsoft.com> wrote in message
news:7BF2B01B-315B-415F-8D7B-4497A9069E40[ at ]microsoft.com...
[Quoted Text] >I have a mainform which identifies a project. On a subform, I would like to
> display a list of team members for that project displayed in data view. I
> cannot keep the entire list accessible in the data view. If I enter a
> name,
> it will be displayed. If i close the main form, and open it later, only a
> blank new cell will be visible, and there is no way to scroll to view the
> other names. Is there a way to do this? One contributing factor may be
> that
> the table used as the basis for the subform contains the names of all team
> members on all projects. Does this preclude the ability to see a dynamic
> list
> of all the names of a particular project at a time?
|
|
Thank you for your response. Although I had created three separate tables, I
am going to streamline those tables further based on your comments.
I still have a question, however, about the display of the subform. When I
open the main form, and look for a list of team members in the subform, in a
dataview, all I see is 1 row of empty cells. (the source for this subform is
the table you mentioned which contains project info and team member info
brought together) I can enter team members there, but I can't scroll down a
list of team members that have already been assigned to that project. Is that
possible?
You're previous response suggested the proper way to relate the tables. I am
wondering if the fact that I can't see a dynamic list of members in the
subform is a result of not properly relating tables, or is it a completely
different problem?
G. Vaught" wrote:
[Quoted Text] > Main forms / sub forms will display related data based on the primary key /
> foreign key relationship. Your subform must contain the primary key from the
> main form, then you can relate the subform to the main form.
>
> Does this make sense to you?
>
> One of the issues you will run into is that a person can be part of more
> than one project. So not only do you have to list the project number, but
> you have to attach the person to each project. Therefore, you will need a
> third table.
>
> Project table that contains only project info: Project Id, Start Date, End
> Date etc.
> Employee table: contains all the employees regardless on whether they work a
> project.
> Projects and Employee Details table: Primary Key from Project table, Primary
> Key from Employee table, any other data that pertains to details of the
> employee on the project.
>
> In the latter table, this is where you will show multiple entries per
> employee, with each project ID. I would set both primary keys as the
> combined key for this table. This will prevent you from listing the same
> individual to the same project id.
>
> Use this latter table to connect to your mainform.
>
>
> "Ryn5000" <Ryn5000[ at ]discussions.microsoft.com> wrote in message
> news:7BF2B01B-315B-415F-8D7B-4497A9069E40[ at ]microsoft.com...
> >I have a mainform which identifies a project. On a subform, I would like to
> > display a list of team members for that project displayed in data view. I
> > cannot keep the entire list accessible in the data view. If I enter a
> > name,
> > it will be displayed. If i close the main form, and open it later, only a
> > blank new cell will be visible, and there is no way to scroll to view the
> > other names. Is there a way to do this? One contributing factor may be
> > that
> > the table used as the basis for the subform contains the names of all team
> > members on all projects. Does this preclude the ability to see a dynamic
> > list
> > of all the names of a particular project at a time?
>
>
>
|
|
|