Can somebody help

[LousieRobinson]

I have created a database in access and I am having trouble with a querie.
The database has a lot of Yes/No for different types of accomidation for a
holday and it also has other filed types which are text one of which is
destination. I would like the querie to show me how many people want each
type of accomidation for a certain destination. I want the accomidation types
to be counted. Each time I run a survey which I think will do this I just get
the same number for each accomidation. Can anybody help as I am new to access
and struggling alot. Thank you.

 

[Tom van Stiphout]

On Sat, 2 May 2009 08:26:01 -0700, LousieRobinson

You may be taking on more than can be expected from a beginner. It
sounds like you have an incorrect database design. I think you have a
table including fields like this:
CustomerID - long int
DestinationID - long int
Accommodation1 - yesno
Accommodation2 - yesno
Accommodation3 - yesno
Accommodation4 - yesno
etc.
And now you want to know which ones are selected.

One reason this is difficult is because you have the wrong database
design. You have what's called "repeating groups" and it is a
violation of Database Normalization rules. Access is not Excel. You
should work with an experienced database designer to assist you. Once
you have a good design, queries like the one you want will be much
easier to do.

-Tom.
Microsoft Access MVP

 

[tina]

you've made a common "newbie" mistake, Lousie - creating a table that looks
like a spreadsheet. Access isn't an "out of the box" application that you
can dive into and create a workable database without any training and study,
and/or prior knowledge of relational design. i'm not trying to discourage
you from using Access. it's a great tool, and allows people with no formal
programming education (like me, and many other folks in these newsgroups) to
build relational databases and amazing user applications. BUT, the software
has a steep learning curve, and you have to learn the basics of relational
design BEFORE you can use the software *effectively* to build anything.

i strongly urge you to STOP now, and study up on relational design
principles. once you understand the basics, then you can advance to using
the tool to build tables/relationships to house your data, and from there
move on to building queries, forms, reports for the user to interact with
the data. for more information see
http://home.att.net/~california.db/tips.html, starting with tips 1 and 2,
and then moving on to tips 3 thru 9.

hth