vb help in Ms Access: combining selection and group by total

[testar]

Hi there,

I am trying to do a similar thing here with access n vb but with a few additions. Please take a look.

I have a table that looks like this:

ID Product Total
1 aaa 10
2 aaa 19
1 bbb 2
3 aaa 1
2 bbb 3
1 ccc 9
3 bbb 3
...& so on

the ID identifies which month it is.

What i am trying to do is to be able to choose which month (ID) i want say '1' and '3'
and it will hopefully give me a grand total of:

aaa 11
bbb 5

im a real newbie and i have tried changing codes that have been posted here but so far no luck


Big Thanks in advance :)

Matt

[testar]

Lol put in a bad intro. i was going to post a reply post to one of the discussions but i thought otherwise so i just copy/paste into a new post without changing the opening sentence. sorry folks.

Matt

Hi there,

I am trying to do a similar thing here with access n vb but with a few additions. Please take a look.

I have a table that looks like this:

ID Product Total
1 aaa 10
2 aaa 19
1 bbb 2
3 aaa 1
2 bbb 3
1 ccc 9
3 bbb 3
...& so on

the ID identifies which month it is.

What i am trying to do is to be able to choose which month (ID) i want say '1' and '3'
and it will hopefully give me a grand total of:

aaa 11
bbb 5

im a real newbie and i have tried changing codes that have been posted here but so far no luck


Big Thanks in advance :)

Matt

[JustJim]

Lol put in a bad intro. i was going to post a reply post to one of the discussions but i thought otherwise so i just copy/paste into a new post without changing the opening sentence. sorry folks.

Matt

Hi Matt,

First of all, perhaps ID is not the best field description for a field which represents months.
Anyway... Air code follows (I'm on a train and can't check the code in Access just now)

SELECT Product, Sum(Total) as GrandTotal
FROM YourTableName
WHERE ID = 1 or ID = 3

should do the trick. Of course it would be more elegant if you work towards letting the code know what months you want before it runs.... but that's another lesson.

Jim

PS I can't help thinking that a GROUP BY clause would be required here. Try it in query design mode and then check the SQL view.
Jim