A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Running & Setting Up Queries
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Please help me!!!



 
 
Thread Tools Display Modes
  #1  
Old May 26th, 2004, 05:14 PM
Ann
external usenet poster
 
Posts: n/a
Default Please help me!!!

Hi to anyone who can help.

I have a table with the following fields:

Last Name
First Name
Course ID 1
Course date req 1
Course ID 2
Course date req 2
Course ID 3
Course date req 3
Course ID 4
Course date req 4
Course ID 5
Course date req 5
Course ID 6
Course date req 6

Each of these date fields stores the date that the
employee requested the course.
Each of the ID fields contains the name of the course.

I am trying to create a crosstab to see which employees
requested which course but I have no idea what I am doing
wrong - the information is just not coming out and I an
not sure which field should be my value field???
Hope this is clear...

Kind regards

Ann


  #2  
Old May 26th, 2004, 05:29 PM
Rick B
external usenet poster
 
Posts: n/a
Default Please help me!!!

Just an observation...

It appears that your table structure is wrong. If I see it correctly, you
have employees and they can request and complete classes. Employee 1 might
requests a particular class (How to build a Widget) for their first course.
Employee 2 might request a different class (How to Sell Widgets) for their
first class.

If my assumption is correct, you should have a table for the employee, a
separate table where the course names and descriptions are stored (if you
want to be able to look them up, and a third table where you would have the
employee number or key, the course, and the date. The third table would
have a variable number of records. If an employee had requested one course,
they would only have one record in table3. If an employee had taken 8
courses, they would have 8 records.

This scenario is a classic one-to-many relationship.

That being said, if my assumptions are correct, and you wissh to normalize
your structure, then your reports and queries would need to be completely
changed.

If my assumption is completely wrong (it has happened once) then let us know
what specific errors you are having with the results of your query and maybe
we can help. How did you build it? What are the results? Etc.

Rick B

"Ann" wrote in message
...
Hi to anyone who can help.

I have a table with the following fields:

Last Name
First Name
Course ID 1
Course date req 1
Course ID 2
Course date req 2
Course ID 3
Course date req 3
Course ID 4
Course date req 4
Course ID 5
Course date req 5
Course ID 6
Course date req 6

Each of these date fields stores the date that the
employee requested the course.
Each of the ID fields contains the name of the course.

I am trying to create a crosstab to see which employees
requested which course but I have no idea what I am doing
wrong - the information is just not coming out and I an
not sure which field should be my value field???
Hope this is clear...

Kind regards

Ann



  #3  
Old May 26th, 2004, 06:17 PM
Ann
external usenet poster
 
Posts: n/a
Default Please help me!!!

Thanks Rick

I think I better think it out again!!

I see to have all the tables so maybe I should include the
related ones and pull the info from there.

Will try this out and get back if I get stuck again.

Many thanks and kind regards from Ireland

Ann

-----Original Message-----
Just an observation...

It appears that your table structure is wrong. If I see

it correctly, you
have employees and they can request and complete

classes. Employee 1 might
requests a particular class (How to build a Widget) for

their first course.
Employee 2 might request a different class (How to Sell

Widgets) for their
first class.

If my assumption is correct, you should have a table for

the employee, a
separate table where the course names and descriptions

are stored (if you
want to be able to look them up, and a third table where

you would have the
employee number or key, the course, and the date. The

third table would
have a variable number of records. If an employee had

requested one course,
they would only have one record in table3. If an

employee had taken 8
courses, they would have 8 records.

This scenario is a classic one-to-many relationship.

That being said, if my assumptions are correct, and you

wissh to normalize
your structure, then your reports and queries would need

to be completely
changed.

If my assumption is completely wrong (it has happened

once) then let us know
what specific errors you are having with the results of

your query and maybe
we can help. How did you build it? What are the

results? Etc.

Rick B

"Ann" wrote in message
...
Hi to anyone who can help.

I have a table with the following fields:

Last Name
First Name
Course ID 1
Course date req 1
Course ID 2
Course date req 2
Course ID 3
Course date req 3
Course ID 4
Course date req 4
Course ID 5
Course date req 5
Course ID 6
Course date req 6

Each of these date fields stores the date that the
employee requested the course.
Each of the ID fields contains the name of the course.

I am trying to create a crosstab to see which employees
requested which course but I have no idea what I am doing
wrong - the information is just not coming out and I an
not sure which field should be my value field???
Hope this is clear...

Kind regards

Ann



.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 09:25 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.