Running in the background

[franc sutherland]

Hello all,

I send out a newsletter using Access 2003 which pauses for 60 seconds
before moving on to the next recipient in the list. This works fine
for being able to have individual emails for each person in the
query. However, it locks up the computer until all the emails are
sent.

Is there a way of making Access perform this type of task in the
background so that I can get on with other things in the meantime?

Thanks,

Franc.

[lyle fairfield]

How is the e-mail sent?
How is the 60 second wait effected?
Why not include multiple recipients in one send?

OT: (Google Groups is presenting me with a different (new?) reply
interface which seems to place my post at the top.)

franc sutherland wrote:

Hello all,

I send out a newsletter using Access 2003 which pauses for 60 seconds
before moving on to the next recipient in the list. This works fine
for being able to have individual emails for each person in the
query. However, it locks up the computer until all the emails are
sent.

Is there a way of making Access perform this type of task in the
background so that I can get on with other things in the meantime?

Thanks,

Franc.

[paii, Ron]

"franc sutherland" <fr**************@googlemail.comwrote in message
news:0e**********************************@w7g2000h sa.googlegroups.com...

Hello all,

I send out a newsletter using Access 2003 which pauses for 60 seconds
before moving on to the next recipient in the list. This works fine
for being able to have individual emails for each person in the
query. However, it locks up the computer until all the emails are
sent.

Is there a way of making Access perform this type of task in the
background so that I can get on with other things in the meantime?

Thanks,

Franc.

"DoEvents" Yields execution so that the operating system can process other
events.
Also see Access help.

[Tom van Stiphout]

On Fri, 25 Apr 2008 05:05:51 -0700 (PDT), lyle fairfield
<ly************@gmail.comwrote:

OT:
Rats, I thought I had finally convinced you :-)
-Tom.

>How is the e-mail sent?
How is the 60 second wait effected?
Why not include multiple recipients in one send?

OT: (Google Groups is presenting me with a different (new?) reply
interface which seems to place my post at the top.)

franc sutherland wrote:

>Hello all,

I send out a newsletter using Access 2003 which pauses for 60 seconds
before moving on to the next recipient in the list. This works fine
for being able to have individual emails for each person in the
query. However, it locks up the computer until all the emails are
sent.

Is there a way of making Access perform this type of task in the
background so that I can get on with other things in the meantime?

Thanks,

Franc.

[lyle fairfield]

It brought up that interface only once Tom. Were they testing
something new for an instant? I hope so.
On Apr 25, 8:47*pm, Tom van Stiphout <[e-mail]:

On Fri, 25 Apr 2008 05:05:51 -0700 (PDT), lyle fairfield

<[e-mail]:

OT:
Rats, I thought I had finally convinced you * :-)
-Tom.

How is the e-mail sent?
How is the 60 second wait effected?
Why not include multiple recipients in one send?

OT: (Google Groups is presenting me with a different (new?) reply
interface which seems to place my post at the top.)

franc sutherland wrote:

Hello all,

I send out a newsletter using Access 2003 which pauses for 60 seconds
before moving on to the next recipient in the list. *This works fine
for being able to have individual emails for each person in the
query. *However, it locks up the computer until all the emails are
sent.

Is there a way of making Access perform this type of task in the
background so that I can get on with other things in the meantime?

Thanks,

Franc.

[franc sutherland]

On Apr 25, 1:05 pm, lyle fairfield <[e-mail]:

How is the e-mail sent?
How is the 60 second wait effected?
Why not include multiple recipients in one send?

OT: (Google Groups is presenting me with a different (new?) reply
interface which seems to place my post at the top.)

franc sutherland wrote:

Hello all,

I send out a newsletter using Access 2003 which pauses for 60 seconds
before moving on to the next recipient in the list. This works fine
for being able to have individual emails for each person in the
query. However, it locks up the computer until all the emails are
sent.

Is there a way of making Access perform this type of task in the
background so that I can get on with other things in the meantime?

Thanks,

Franc.

Hello Lyle,

Thanks for your reply.

I send out the emails using DoCmd.SendObject in a looping structure
which counts 60 seconds from now() before processing the next DoCmd
command. I don't do multiple recipients as each email is
personalised.

Franc.

[Larry Linson]

"lyle fairfield" <ly************@gmail.comwrote

OT: (Google Groups is presenting me with a different
(new?) reply interface which seems to place my post at the top.)

One of my pet peeves is web or UI designers without direct experience in
using the application, and little real competence in user interface, who
decide we need a "richer user experience" and change things that work well
and flexibly, into something that works not nearly so well, nor so flexibly.

I should probably not complain, because just that kind of web designer at a
third-party provider of info to a client for whom I was doing code to scrape
data from a screen gave me continuing employment with "richer user
experiences" once or twice a week until I finally convinced the client to
ask the third-party to give them a download option (after all, they were the
third-party's largest customer for that data).

Larry Linson
Microsoft Office Access MVP

[franc sutherland]

On May 8, 7:44 pm, "Larry Linson" <[e-mail]:

"lyle fairfield" <[e-mail]

OT: (Google Groups is presenting me with a different
(new?) reply interface which seems to place my post at the top.)

One of my pet peeves is web or UI designers without direct experience in
using the application, and little real competence in user interface, who
decide we need a "richer user experience" and change things that work well
and flexibly, into something that works not nearly so well, nor so flexibly.

I should probably not complain, because just that kind of web designer at a
third-party provider of info to a client for whom I was doing code to scrape
data from a screen gave me continuing employment with "richer user
experiences" once or twice a week until I finally convinced the client to
ask the third-party to give them a download option (after all, they were the
third-party's largest customer for that data).

Larry Linson
Microsoft Office Access MVP

Hi Larry,

Do you have any advice on my question about running in the background?

Cheers,

Franc.