summing a sum

[colenzo]

I'm probably going to sound really stupid asking this but;

I have a select query in which the individual componants are all total sum'ing the records from the tables.

However - how can I sum up the summed values. If I try writing an expressions (ie. [sumofPUBPST] + [sumofPUBTEL]) it refuses to bring up a value leaving a black query field;

Am I missing something because to me it makes perfect sense to be able to do that but apparently access doesn't like it very much.

 

[vbaInet]

What do you mean by a black query field?

Format the texboxes [sumofPUBPST] and [sumofPUBTEL] as General Number in the Format property. Yes you're right, you can add up the sums, but it also depends which section you put the code and whether the control names are correct.

Edit: Scrap the above, I thought this was a report issue.

Create another report based on the sum query and add them in this new query.

 

[colenzo]

What do you mean by a black query field?

Format the texboxes [sumofPUBPST] and [sumofPUBTEL] as General Number in the Format property. Yes you're right, you can add up the sums, but it also depends which section you put the code and whether the control names are correct.

Edit: Scrap the above, I thought this was a report issue.

Create another report based on the sum query and add them in this new query.

ok i'm confused now - i'm dealing strictly with the query - forget the report, that i will sort - and sorry i didnt mean black - i meant blank! ie. its not bringing up a value at all. I'm really confused as to why its doing this!

 

[vbaInet]

Create another report based on the sum query and add them in this new query.

I still made the same mistake That should have been query, not report.

 

[colenzo]

I still made the same mistake That should have been query, not report.

between the both of us apparently we can't get our words out right!

ah... so i'm multi layering them then? just out of interest.. is there a limit on how much you can do with layering - just interested because I tried writing a query earlier and got a message of "query is too complex" or something like that. I've broken it down now but it's just an interest thing really - for me it made sense to keep it all together but apparently not!

 

[vbaInet]

It looks like it

Yes, you are simply letting the first query run before trying to calculate on the results. There should be a limit but it would most likely be in the hundreds. You got the "too complex" error due to the joins being incorrect or you have too many tables you're joining on.

 

[colenzo]

It looks like it

Yes, you are simply letting the first query run before trying to calculate on the results. There should be a limit but it would most likely be in the hundreds. You got the "too complex" error due to the joins being incorrect or you have too many tables you're joining on.

ah I see! that makes sense now - it's probably the joins but atleast i know what part to look at!

now why can't there be books out there that explain things like that - everything seems to be full of terminology and stuff thats just too weird to understand!
Write a book dude - i'd buy it!

 

[vbaInet]

Write a book dude - i'd buy it!

Access isn't my full time hobby so I don't think I will be able to follow the times

now why can't there be books out there that explain things like that - everything seems to be full of terminology and stuff thats just too weird to understand!

This is why we're here to help But (I think) there are some good books out there.