query across 16 columns but only have 9 rows!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Please excuse this question as I am a newbie.
I have a query with 20 columns. First four are part number and details. The
other 16 are just activities that store week numbers.
I need to search on the 16 number fields and if the criteria matches the
week number I enter, it should show itself and the first four columns in a
report. I have done this but with limitations.
I understand that I can use criteria in one cell then drop down and across
and add the same criteria in the ‘or’. What I cannot do is keep repeating
this as I only have 9 rows in total to populate. I could do with 16. How can
I overcome this or perform this task more economically?
Regards
Warren.
 
warren said:
Please excuse this question as I am a newbie.
I have a query with 20 columns. First four are part number and details.
The
other 16 are just activities that store week numbers.
I need to search on the 16 number fields and if the criteria matches the
week number I enter, it should show itself and the first four columns in a
report. I have done this but with limitations.
I understand that I can use criteria in one cell then drop down and across
and add the same criteria in the ‘or’. What I cannot do is keep repeating
this as I only have 9 rows in total to populate. I could do with 16. How
can
I overcome this or perform this task more economically?
Regards
Warren.
Click to expand...


You can add rows. If using Access 2007, you'll find "Insert Rows" in the
"Query Setup" section of the "Design" tab of the ribbon in query design
view. In earlier versions you'll find "Rows" in the "Insert" menu.

Alternatively, you can switch to SQL view. In Access 2007, you can choose
"SQL View" from the "View" drop-down that appears at the far left of both
the "Home" and "Design" tabs of the ribbon in query design view. In earlier
versions, choose "SQL View" from the "View" menu.

I suspect, however, that the real problem here is a flawed database design.
From your description, it appears likely to me that those 16 columns should
have been rows in a related table.
 
Brandan, thank you, thank you, thank you.

Ive been right hand mouse clicking, Dooh!
Your first paragraph did the trick.

I couldn’t agree more about the flawed database design and if you have any
typical examples or suggestions that i could have a look at then I will be
very grateful.

In short, one tool number with 3 other search fields and 16 activities that
have to be carried out on a certain week throughout the year, or more exactly
4 activities that have to be carried out several times throughout the year.
Today Brandan, you are a king among men, thank you again.
Regards
Warren.
 
Back
Top