473,834 Members | 2,095 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Need Ideas For Layout Of Form

Tom
I am looking for some ideas for how to design the layout of the form for
data entry and to display the data for the following situation:
There are many sales associates. A sales associate can work for multiple
companies and work for multiple divisions within each company. Within each
division he can work in multiple departments and within each department he
can work with multiple groups. In each group he works on multiple projects.
All the work areas of each sales associates needs to be input in the form
and displayed in the form - Companies, Divisions, Departments, Groups and
Projects.There are one-to-many relationships between company and division,
division and dpartment, department and group and group and project.

Thanks for all help,

Tom
Nov 13 '05 #1
10 2895
Tom, the question is not so much about the form, as it is about getting the
data structure right.

To my way of thinking, companies, divisions, and departments are actually
layers of the same kind of entity, whereas projects are a different kind of
entity. A project might be shared amongst different departments or
divisions, and could have a starting and ending date, whereas a department
would be a (normally) permanent section of just one division and so forth up
the tree.

If that is so, you might consider making a "Client" table where you can
store all the first kind of entity. It will have a ClientID field as primary
key, and a ParentID field that indicates the immediate parent of this
client. So, if the "client" is a division type, its ParentID would be the
ClientID of a record that is a company.

You would then have another table for Projects, and a table for Staff.
Another table might then have fields:
ClientID: foreign key to Client.ClientID (so can be a co, dept, div,
....)
ProjectID: foreign key to Project.Project ID
StaffID: foreign key to Staff.StaffID
WorkDate: date the work was done.
Each record says something like this: on August 1 (work date), Joe Smith
(staff) worked for the IT Department (client) on project 49 (whatever that
is.)

If that copes with what you need, you would then have a form with 3 combos
and a text box for the date. Chances are, that's not exactly what you need,
but hopefully it gets you thinking in a useful direction.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:rY******** ********@newsre ad1.news.atl.ea rthlink.net...
I am looking for some ideas for how to design the layout of the form for
data entry and to display the data for the following situation:
There are many sales associates. A sales associate can work for multiple
companies and work for multiple divisions within each company. Within each
division he can work in multiple departments and within each department he
can work with multiple groups. In each group he works on multiple
projects. All the work areas of each sales associates needs to be input in
the form and displayed in the form - Companies, Divisions, Departments,
Groups and Projects.There are one-to-many relationships between company
and division, division and dpartment, department and group and group and
project.

Thanks for all help,

Tom

Nov 13 '05 #2
Tom, the question is not so much about the form, as it is about getting the
data structure right.

To my way of thinking, companies, divisions, and departments are actually
layers of the same kind of entity, whereas projects are a different kind of
entity. A project might be shared amongst different departments or
divisions, and could have a starting and ending date, whereas a department
would be a (normally) permanent section of just one division and so forth up
the tree.

If that is so, you might consider making a "Client" table where you can
store all the first kind of entity. It will have a ClientID field as primary
key, and a ParentID field that indicates the immediate parent of this
client. So, if the "client" is a division type, its ParentID would be the
ClientID of a record that is a company.

You would then have another table for Projects, and a table for Staff.
Another table might then have fields:
ClientID: foreign key to Client.ClientID (so can be a co, dept, div,
....)
ProjectID: foreign key to Project.Project ID
StaffID: foreign key to Staff.StaffID
WorkDate: date the work was done.
Each record says something like this: on August 1 (work date), Joe Smith
(staff) worked for the IT Department (client) on project 49 (whatever that
is.)

If that copes with what you need, you would then have a form with 3 combos
and a text box for the date. Chances are, that's not exactly what you need,
but hopefully it gets you thinking in a useful direction.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:rY******** ********@newsre ad1.news.atl.ea rthlink.net...
I am looking for some ideas for how to design the layout of the form for
data entry and to display the data for the following situation:
There are many sales associates. A sales associate can work for multiple
companies and work for multiple divisions within each company. Within each
division he can work in multiple departments and within each department he
can work with multiple groups. In each group he works on multiple
projects. All the work areas of each sales associates needs to be input in
the form and displayed in the form - Companies, Divisions, Departments,
Groups and Projects.There are one-to-many relationships between company
and division, division and dpartment, department and group and group and
project.

Thanks for all help,

Tom

Nov 13 '05 #3
Tom
Allen,

Thanks for the response!

I need records to say:
On August 1 (work date), Joe Smith worked for the Industrial Group (group)
of the IT Department (department) of the ABC Division (division) of IT Inc.
(company) on project 49 (project).

On August 1 (work date), Joe Smith worked for the Refining Group (group) of
the Engineering Department (department) of the Construction Division
(division) of IT Inc. (company) on project 27 (project).

On August 1 (work date), Joe Smith worked for the Marketing Group (group) of
the Sales Department (department) of the XYZ Division (division) of IT Inc.
(company) on project 84 (project).

I need a form to enter these records for Joe Smith for August 1.

Thanks,

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
Tom, the question is not so much about the form, as it is about getting
the data structure right.

To my way of thinking, companies, divisions, and departments are actually
layers of the same kind of entity, whereas projects are a different kind
of entity. A project might be shared amongst different departments or
divisions, and could have a starting and ending date, whereas a department
would be a (normally) permanent section of just one division and so forth
up the tree.

If that is so, you might consider making a "Client" table where you can
store all the first kind of entity. It will have a ClientID field as
primary key, and a ParentID field that indicates the immediate parent of
this client. So, if the "client" is a division type, its ParentID would be
the ClientID of a record that is a company.

You would then have another table for Projects, and a table for Staff.
Another table might then have fields:
ClientID: foreign key to Client.ClientID (so can be a co, dept,
div, ...)
ProjectID: foreign key to Project.Project ID
StaffID: foreign key to Staff.StaffID
WorkDate: date the work was done.
Each record says something like this: on August 1 (work date), Joe Smith
(staff) worked for the IT Department (client) on project 49 (whatever that
is.)

If that copes with what you need, you would then have a form with 3 combos
and a text box for the date. Chances are, that's not exactly what you
need, but hopefully it gets you thinking in a useful direction.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:rY******** ********@newsre ad1.news.atl.ea rthlink.net...
I am looking for some ideas for how to design the layout of the form for
data entry and to display the data for the following situation:
There are many sales associates. A sales associate can work for multiple
companies and work for multiple divisions within each company. Within
each division he can work in multiple departments and within each
department he can work with multiple groups. In each group he works on
multiple projects. All the work areas of each sales associates needs to
be input in the form and displayed in the form - Companies, Divisions,
Departments, Groups and Projects.There are one-to-many relationships
between company and division, division and dpartment, department and
group and group and project.

Thanks for all help,

Tom


Nov 13 '05 #4
Tom
Allen,

Thanks for the response!

I need records to say:
On August 1 (work date), Joe Smith worked for the Industrial Group (group)
of the IT Department (department) of the ABC Division (division) of IT Inc.
(company) on project 49 (project).

On August 1 (work date), Joe Smith worked for the Refining Group (group) of
the Engineering Department (department) of the Construction Division
(division) of IT Inc. (company) on project 27 (project).

On August 1 (work date), Joe Smith worked for the Marketing Group (group) of
the Sales Department (department) of the XYZ Division (division) of IT Inc.
(company) on project 84 (project).

I need a form to enter these records for Joe Smith for August 1.

Thanks,

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
Tom, the question is not so much about the form, as it is about getting
the data structure right.

To my way of thinking, companies, divisions, and departments are actually
layers of the same kind of entity, whereas projects are a different kind
of entity. A project might be shared amongst different departments or
divisions, and could have a starting and ending date, whereas a department
would be a (normally) permanent section of just one division and so forth
up the tree.

If that is so, you might consider making a "Client" table where you can
store all the first kind of entity. It will have a ClientID field as
primary key, and a ParentID field that indicates the immediate parent of
this client. So, if the "client" is a division type, its ParentID would be
the ClientID of a record that is a company.

You would then have another table for Projects, and a table for Staff.
Another table might then have fields:
ClientID: foreign key to Client.ClientID (so can be a co, dept,
div, ...)
ProjectID: foreign key to Project.Project ID
StaffID: foreign key to Staff.StaffID
WorkDate: date the work was done.
Each record says something like this: on August 1 (work date), Joe Smith
(staff) worked for the IT Department (client) on project 49 (whatever that
is.)

If that copes with what you need, you would then have a form with 3 combos
and a text box for the date. Chances are, that's not exactly what you
need, but hopefully it gets you thinking in a useful direction.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:rY******** ********@newsre ad1.news.atl.ea rthlink.net...
I am looking for some ideas for how to design the layout of the form for
data entry and to display the data for the following situation:
There are many sales associates. A sales associate can work for multiple
companies and work for multiple divisions within each company. Within
each division he can work in multiple departments and within each
department he can work with multiple groups. In each group he works on
multiple projects. All the work areas of each sales associates needs to
be input in the form and displayed in the form - Companies, Divisions,
Departments, Groups and Projects.There are one-to-many relationships
between company and division, division and dpartment, department and
group and group and project.

Thanks for all help,

Tom


Nov 13 '05 #5
So, you have a couple of choices.

Standard structure
==============
Create:
- a table of possible Group values (records for "Industrial ", etc);
- another table to hold the Department values (records for "IT", etc.)
- another table for Division values.
- another table for Companies.
- the main table that will have fields:
o GroupID
o DepartmentID
o DivisionID
o CompanyID
o StaffID
o WorkDate

The disadvantage of that approach is that you can end up choosing nonsense
combinations, such as the Welfare department of a Law form. :-)

Alternative structure
==============
The other structre suggested earlier has the disadvantage that you do have
to go through and enter each division that applies to each company, and then
each deparment of each division, and so on. While this takes more effort
initially, it may provide better data, and it copes with internal company
structures that may not match the standard one (e.g. small companies don't
have departments of divisions.)

Either way, once you have the tables in place, and the relationships between
them, you can start to think about how to create forms.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:5T******** ********@newsre ad1.news.atl.ea rthlink.net...
Allen,

Thanks for the response!

I need records to say:
On August 1 (work date), Joe Smith worked for the Industrial Group (group)
of the IT Department (department) of the ABC Division (division) of IT
Inc. (company) on project 49 (project).

On August 1 (work date), Joe Smith worked for the Refining Group (group)
of the Engineering Department (department) of the Construction Division
(division) of IT Inc. (company) on project 27 (project).

On August 1 (work date), Joe Smith worked for the Marketing Group (group)
of the Sales Department (department) of the XYZ Division (division) of IT
Inc. (company) on project 84 (project).

I need a form to enter these records for Joe Smith for August 1.

Thanks,

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
Tom, the question is not so much about the form, as it is about getting
the data structure right.

To my way of thinking, companies, divisions, and departments are actually
layers of the same kind of entity, whereas projects are a different kind
of entity. A project might be shared amongst different departments or
divisions, and could have a starting and ending date, whereas a
department would be a (normally) permanent section of just one division
and so forth up the tree.

If that is so, you might consider making a "Client" table where you can
store all the first kind of entity. It will have a ClientID field as
primary key, and a ParentID field that indicates the immediate parent of
this client. So, if the "client" is a division type, its ParentID would
be the ClientID of a record that is a company.

You would then have another table for Projects, and a table for Staff.
Another table might then have fields:
ClientID: foreign key to Client.ClientID (so can be a co, dept,
div, ...)
ProjectID: foreign key to Project.Project ID
StaffID: foreign key to Staff.StaffID
WorkDate: date the work was done.
Each record says something like this: on August 1 (work date), Joe Smith
(staff) worked for the IT Department (client) on project 49 (whatever
that is.)

If that copes with what you need, you would then have a form with 3
combos and a text box for the date. Chances are, that's not exactly what
you need, but hopefully it gets you thinking in a useful direction.

"Tom" <no***@email.co m> wrote in message
news:rY******** ********@newsre ad1.news.atl.ea rthlink.net...
I am looking for some ideas for how to design the layout of the form for
data entry and to display the data for the following situation:
There are many sales associates. A sales associate can work for multiple
companies and work for multiple divisions within each company. Within
each division he can work in multiple departments and within each
department he can work with multiple groups. In each group he works on
multiple projects. All the work areas of each sales associates needs to
be input in the form and displayed in the form - Companies, Divisions,
Departments, Groups and Projects.There are one-to-many relationships
between company and division, division and dpartment, department and
group and group and project.

Nov 13 '05 #6
So, you have a couple of choices.

Standard structure
==============
Create:
- a table of possible Group values (records for "Industrial ", etc);
- another table to hold the Department values (records for "IT", etc.)
- another table for Division values.
- another table for Companies.
- the main table that will have fields:
o GroupID
o DepartmentID
o DivisionID
o CompanyID
o StaffID
o WorkDate

The disadvantage of that approach is that you can end up choosing nonsense
combinations, such as the Welfare department of a Law form. :-)

Alternative structure
==============
The other structre suggested earlier has the disadvantage that you do have
to go through and enter each division that applies to each company, and then
each deparment of each division, and so on. While this takes more effort
initially, it may provide better data, and it copes with internal company
structures that may not match the standard one (e.g. small companies don't
have departments of divisions.)

Either way, once you have the tables in place, and the relationships between
them, you can start to think about how to create forms.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:5T******** ********@newsre ad1.news.atl.ea rthlink.net...
Allen,

Thanks for the response!

I need records to say:
On August 1 (work date), Joe Smith worked for the Industrial Group (group)
of the IT Department (department) of the ABC Division (division) of IT
Inc. (company) on project 49 (project).

On August 1 (work date), Joe Smith worked for the Refining Group (group)
of the Engineering Department (department) of the Construction Division
(division) of IT Inc. (company) on project 27 (project).

On August 1 (work date), Joe Smith worked for the Marketing Group (group)
of the Sales Department (department) of the XYZ Division (division) of IT
Inc. (company) on project 84 (project).

I need a form to enter these records for Joe Smith for August 1.

Thanks,

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
Tom, the question is not so much about the form, as it is about getting
the data structure right.

To my way of thinking, companies, divisions, and departments are actually
layers of the same kind of entity, whereas projects are a different kind
of entity. A project might be shared amongst different departments or
divisions, and could have a starting and ending date, whereas a
department would be a (normally) permanent section of just one division
and so forth up the tree.

If that is so, you might consider making a "Client" table where you can
store all the first kind of entity. It will have a ClientID field as
primary key, and a ParentID field that indicates the immediate parent of
this client. So, if the "client" is a division type, its ParentID would
be the ClientID of a record that is a company.

You would then have another table for Projects, and a table for Staff.
Another table might then have fields:
ClientID: foreign key to Client.ClientID (so can be a co, dept,
div, ...)
ProjectID: foreign key to Project.Project ID
StaffID: foreign key to Staff.StaffID
WorkDate: date the work was done.
Each record says something like this: on August 1 (work date), Joe Smith
(staff) worked for the IT Department (client) on project 49 (whatever
that is.)

If that copes with what you need, you would then have a form with 3
combos and a text box for the date. Chances are, that's not exactly what
you need, but hopefully it gets you thinking in a useful direction.

"Tom" <no***@email.co m> wrote in message
news:rY******** ********@newsre ad1.news.atl.ea rthlink.net...
I am looking for some ideas for how to design the layout of the form for
data entry and to display the data for the following situation:
There are many sales associates. A sales associate can work for multiple
companies and work for multiple divisions within each company. Within
each division he can work in multiple departments and within each
department he can work with multiple groups. In each group he works on
multiple projects. All the work areas of each sales associates needs to
be input in the form and displayed in the form - Companies, Divisions,
Departments, Groups and Projects.There are one-to-many relationships
between company and division, division and dpartment, department and
group and group and project.

Nov 13 '05 #7
Tom
I have the standard table structure and now I'm looking for ideas for a
user-friendly form.

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
So, you have a couple of choices.

Standard structure
==============
Create:
- a table of possible Group values (records for "Industrial ", etc);
- another table to hold the Department values (records for "IT", etc.)
- another table for Division values.
- another table for Companies.
- the main table that will have fields:
o GroupID
o DepartmentID
o DivisionID
o CompanyID
o StaffID
o WorkDate

The disadvantage of that approach is that you can end up choosing nonsense
combinations, such as the Welfare department of a Law form. :-)

Alternative structure
==============
The other structre suggested earlier has the disadvantage that you do have
to go through and enter each division that applies to each company, and
then each deparment of each division, and so on. While this takes more
effort initially, it may provide better data, and it copes with internal
company structures that may not match the standard one (e.g. small
companies don't have departments of divisions.)

Either way, once you have the tables in place, and the relationships
between them, you can start to think about how to create forms.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:5T******** ********@newsre ad1.news.atl.ea rthlink.net...
Allen,

Thanks for the response!

I need records to say:
On August 1 (work date), Joe Smith worked for the Industrial Group
(group) of the IT Department (department) of the ABC Division (division)
of IT Inc. (company) on project 49 (project).

On August 1 (work date), Joe Smith worked for the Refining Group (group)
of the Engineering Department (department) of the Construction Division
(division) of IT Inc. (company) on project 27 (project).

On August 1 (work date), Joe Smith worked for the Marketing Group (group)
of the Sales Department (department) of the XYZ Division (division) of IT
Inc. (company) on project 84 (project).

I need a form to enter these records for Joe Smith for August 1.

Thanks,

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
Tom, the question is not so much about the form, as it is about getting
the data structure right.

To my way of thinking, companies, divisions, and departments are
actually layers of the same kind of entity, whereas projects are a
different kind of entity. A project might be shared amongst different
departments or divisions, and could have a starting and ending date,
whereas a department would be a (normally) permanent section of just one
division and so forth up the tree.

If that is so, you might consider making a "Client" table where you can
store all the first kind of entity. It will have a ClientID field as
primary key, and a ParentID field that indicates the immediate parent of
this client. So, if the "client" is a division type, its ParentID would
be the ClientID of a record that is a company.

You would then have another table for Projects, and a table for Staff.
Another table might then have fields:
ClientID: foreign key to Client.ClientID (so can be a co, dept,
div, ...)
ProjectID: foreign key to Project.Project ID
StaffID: foreign key to Staff.StaffID
WorkDate: date the work was done.
Each record says something like this: on August 1 (work date), Joe Smith
(staff) worked for the IT Department (client) on project 49 (whatever
that is.)

If that copes with what you need, you would then have a form with 3
combos and a text box for the date. Chances are, that's not exactly what
you need, but hopefully it gets you thinking in a useful direction.

"Tom" <no***@email.co m> wrote in message
news:rY******** ********@newsre ad1.news.atl.ea rthlink.net...
I am looking for some ideas for how to design the layout of the form for
data entry and to display the data for the following situation:
There are many sales associates. A sales associate can work for
multiple companies and work for multiple divisions within each company.
Within each division he can work in multiple departments and within
each department he can work with multiple groups. In each group he
works on multiple projects. All the work areas of each sales associates
needs to be input in the form and displayed in the form - Companies,
Divisions, Departments, Groups and Projects.There are one-to-many
relationships between company and division, division and dpartment,
department and group and group and project.


Nov 13 '05 #8
Tom
I have the standard table structure and now I'm looking for ideas for a
user-friendly form.

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
So, you have a couple of choices.

Standard structure
==============
Create:
- a table of possible Group values (records for "Industrial ", etc);
- another table to hold the Department values (records for "IT", etc.)
- another table for Division values.
- another table for Companies.
- the main table that will have fields:
o GroupID
o DepartmentID
o DivisionID
o CompanyID
o StaffID
o WorkDate

The disadvantage of that approach is that you can end up choosing nonsense
combinations, such as the Welfare department of a Law form. :-)

Alternative structure
==============
The other structre suggested earlier has the disadvantage that you do have
to go through and enter each division that applies to each company, and
then each deparment of each division, and so on. While this takes more
effort initially, it may provide better data, and it copes with internal
company structures that may not match the standard one (e.g. small
companies don't have departments of divisions.)

Either way, once you have the tables in place, and the relationships
between them, you can start to think about how to create forms.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:5T******** ********@newsre ad1.news.atl.ea rthlink.net...
Allen,

Thanks for the response!

I need records to say:
On August 1 (work date), Joe Smith worked for the Industrial Group
(group) of the IT Department (department) of the ABC Division (division)
of IT Inc. (company) on project 49 (project).

On August 1 (work date), Joe Smith worked for the Refining Group (group)
of the Engineering Department (department) of the Construction Division
(division) of IT Inc. (company) on project 27 (project).

On August 1 (work date), Joe Smith worked for the Marketing Group (group)
of the Sales Department (department) of the XYZ Division (division) of IT
Inc. (company) on project 84 (project).

I need a form to enter these records for Joe Smith for August 1.

Thanks,

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
Tom, the question is not so much about the form, as it is about getting
the data structure right.

To my way of thinking, companies, divisions, and departments are
actually layers of the same kind of entity, whereas projects are a
different kind of entity. A project might be shared amongst different
departments or divisions, and could have a starting and ending date,
whereas a department would be a (normally) permanent section of just one
division and so forth up the tree.

If that is so, you might consider making a "Client" table where you can
store all the first kind of entity. It will have a ClientID field as
primary key, and a ParentID field that indicates the immediate parent of
this client. So, if the "client" is a division type, its ParentID would
be the ClientID of a record that is a company.

You would then have another table for Projects, and a table for Staff.
Another table might then have fields:
ClientID: foreign key to Client.ClientID (so can be a co, dept,
div, ...)
ProjectID: foreign key to Project.Project ID
StaffID: foreign key to Staff.StaffID
WorkDate: date the work was done.
Each record says something like this: on August 1 (work date), Joe Smith
(staff) worked for the IT Department (client) on project 49 (whatever
that is.)

If that copes with what you need, you would then have a form with 3
combos and a text box for the date. Chances are, that's not exactly what
you need, but hopefully it gets you thinking in a useful direction.

"Tom" <no***@email.co m> wrote in message
news:rY******** ********@newsre ad1.news.atl.ea rthlink.net...
I am looking for some ideas for how to design the layout of the form for
data entry and to display the data for the following situation:
There are many sales associates. A sales associate can work for
multiple companies and work for multiple divisions within each company.
Within each division he can work in multiple departments and within
each department he can work with multiple groups. In each group he
works on multiple projects. All the work areas of each sales associates
needs to be input in the form and displayed in the form - Companies,
Divisions, Departments, Groups and Projects.There are one-to-many
relationships between company and division, division and dpartment,
department and group and group and project.


Nov 13 '05 #9
The usual form would be a bunch of combos--one each for GroupID, the
DepartmentID, etc--and a text box to enter the date.

Each combo have a lookup table as the RowSource.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:%L******** ******@newsread 2.news.atl.eart hlink.net...
I have the standard table structure and now I'm looking for ideas for a
user-friendly form.

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
So, you have a couple of choices.

Standard structure
==============
Create:
- a table of possible Group values (records for "Industrial ", etc);
- another table to hold the Department values (records for "IT", etc.)
- another table for Division values.
- another table for Companies.
- the main table that will have fields:
o GroupID
o DepartmentID
o DivisionID
o CompanyID
o StaffID
o WorkDate

The disadvantage of that approach is that you can end up choosing
nonsense combinations, such as the Welfare department of a Law form. :-)

Alternative structure
==============
The other structre suggested earlier has the disadvantage that you do
have to go through and enter each division that applies to each company,
and then each deparment of each division, and so on. While this takes
more effort initially, it may provide better data, and it copes with
internal company structures that may not match the standard one (e.g.
small companies don't have departments of divisions.)

Either way, once you have the tables in place, and the relationships
between them, you can start to think about how to create forms.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tom" <no***@email.co m> wrote in message
news:5T******** ********@newsre ad1.news.atl.ea rthlink.net...
Allen,

Thanks for the response!

I need records to say:
On August 1 (work date), Joe Smith worked for the Industrial Group
(group) of the IT Department (department) of the ABC Division (division)
of IT Inc. (company) on project 49 (project).

On August 1 (work date), Joe Smith worked for the Refining Group (group)
of the Engineering Department (department) of the Construction Division
(division) of IT Inc. (company) on project 27 (project).

On August 1 (work date), Joe Smith worked for the Marketing Group
(group) of the Sales Department (department) of the XYZ Division
(division) of IT Inc. (company) on project 84 (project).

I need a form to enter these records for Joe Smith for August 1.

Thanks,

Tom
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:42******** *************** @per-qv1-newsreader-01.iinet.net.au ...
Tom, the question is not so much about the form, as it is about getting
the data structure right.

To my way of thinking, companies, divisions, and departments are
actually layers of the same kind of entity, whereas projects are a
different kind of entity. A project might be shared amongst different
departments or divisions, and could have a starting and ending date,
whereas a department would be a (normally) permanent section of just
one division and so forth up the tree.

If that is so, you might consider making a "Client" table where you can
store all the first kind of entity. It will have a ClientID field as
primary key, and a ParentID field that indicates the immediate parent
of this client. So, if the "client" is a division type, its ParentID
would be the ClientID of a record that is a company.

You would then have another table for Projects, and a table for Staff.
Another table might then have fields:
ClientID: foreign key to Client.ClientID (so can be a co, dept,
div, ...)
ProjectID: foreign key to Project.Project ID
StaffID: foreign key to Staff.StaffID
WorkDate: date the work was done.
Each record says something like this: on August 1 (work date), Joe
Smith (staff) worked for the IT Department (client) on project 49
(whatever that is.)

If that copes with what you need, you would then have a form with 3
combos and a text box for the date. Chances are, that's not exactly
what you need, but hopefully it gets you thinking in a useful
direction.

"Tom" <no***@email.co m> wrote in message
news:rY******** ********@newsre ad1.news.atl.ea rthlink.net...
>I am looking for some ideas for how to design the layout of the form
>for data entry and to display the data for the following situation:
> There are many sales associates. A sales associate can work for
> multiple companies and work for multiple divisions within each
> company. Within each division he can work in multiple departments and
> within each department he can work with multiple groups. In each group
> he works on multiple projects. All the work areas of each sales
> associates needs to be input in the form and displayed in the form -
> Companies, Divisions, Departments, Groups and Projects.There are
> one-to-many relationships between company and division, division and
> dpartment, department and group and group and project.



Nov 13 '05 #10

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

3
13503
by: Peter | last post by:
For some unknown reason my Form Layout Window has stopped showing a form on it. I can open & close the window, set docking on/off but no form. The right click start-up options are also greyed out. Any idea how I can fix this? Thanks --
5
2551
by: Usenet User | last post by:
A user informed me that some pages I've created with nested tables are spewing out dozens of blank pages at the end of a print run. No one noticed this for a long time, as printer-friendly files are available elsewhere, and the .htm files are intended for online viewing. But still, others will click 'print' in the browser window, so I'd like to stop all that paper from being wasted. The pages seem to validate okay. Any ideas? Is...
3
1597
by: Mike | last post by:
Hey guys I am pulling my hair out on this problem!!!!! Any help or ideas or comments on how to make this work I would be grateful! I have been working on this for the past 4 days and nothing I do seems to get me any closer to the solution. Below is a program that I am working on for a class project. The original code was provided for us which is what I have below. What we have to do is make the app run so that it allows the user to add...
0
332
by: Tom | last post by:
I am looking for some ideas for how to design the layout of the form for data entry and to display the data for the following situation: There are many sales associates. A sales associate can work for multiple companies and work for multiple divisions within each company. Within each division he can work in multiple departments and within each department he can work with multiple groups. In each group he works on multiple projects. All the...
2
2486
by: Steve Richter | last post by:
I am spending too much time thinking of nesting tables within tables to get the form layout that I want. a simple example: Sub heading: property text: entry field property text: entry field Sub heading: property text: entry field
10
9220
by: Luke | last post by:
Hi. I am trying to make correct layout, here is an example of (dynamically generated content via jsp): http://localhost/www/layout.htm Most outer div is positioned absolute (if not then it will not grow when content inside div.body is greater than width of window of user agent), anyway anyone knowlegable can see it in sources...
3
1547
by: Samuel Shulman | last post by:
I am looking for good guidance for positioning controls on the form.document, it is absolute nightmare and I don't know where to begin Thank you, Samuel Shulman
2
2333
by: Brian Tkatch | last post by:
Not sure if this is the way it's supposed to be, but after a Layout event on an MDI form, the form's new width is set, but the MDIClient's width is not. As an example, start a new Windows Application, and for the code use: Public Class Form1 Dim TextBox1, TextBox2, TextBox3 As New TextBox Dim The_MDIClient As MdiClient
1
2444
by: dlogan | last post by:
Since this is becoming a complete hack-job, I think its about time I asked for some help. I am trying to make a calendar using AJAX to allow for the main calendar to display, then load in the events afterwards for any given week. Each step along the way I find some hack to make it work but its becoming with all the problems I've been running into I'm thinking I'm not attacking it right. Here's the output of the iframe in question (I know...
0
9796
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look ! Part I. Meaning of...
0
9643
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
0
10214
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
1
7755
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms. Adolph will...
0
6951
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert into image. Globals.ThisAddIn.Application.ActiveDocument.Select();...
0
5624
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
0
5790
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
4425
by: 6302768590 | last post by:
Hai team i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
2
3975
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.