Search results

Hum... I'm stumped. Sorry...

You are correct. As a rule of thumb you should not save query results in tables...

Look at this and see if the const suggestion works in your code: http://bytes.com/topic/access/answers/833088-sending-email-cdo-access

So... I know this is going to be redundant but - Did you see if the barebone database/code worked on the machine that the original code works on?

in your bare bones test did you take things like [Action], etc? edit: Post your bare bones test code

Access needs to know where the code is for the outlook objects. If you go: VBA window->Tools->References on the machine that does work and make sure you have the same ones checked in the machine that does not work ?

Have you checked to see if the references have been set up to see the outlook objects?

How many records total would you need to go through in one run of the query? You could create a function to do it...

Have you opened outlook and sent an email manually?

Have you tried stepping through the code as it executes?

Post the email code

Remove the entire column(s) you don't want (need), not just the grouping clause...

My first guess is that you're grouping on too many columns...

Not sure about the code but you used to have to use twips or something like that to locate things on a form...

You should be able to do this with a group by and dmax()...

Using an autonumber in this manner is not recommended. Counted stuff is usually possible using other means...

I think I would create a barebones email routine database on the machine(s) that do not work to see if it's the machine or the app - ?

Welcome Cwire -

Maybe throw in a set focus to a control on the report when it opens?

Please not another queer thread...:banghead: