e-mail by macro

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a databse on a win2000 machine using Access 2000 that sends out
e-mails automatically (or it used to). Recently I had to install servicepack
3 to correct some errors in the autoname correct feature. Now all my e-mails
request user input before they can go out (so much for automation). Anybody
know the workaround for this fine feature?
 
I have a databse on a win2000 machine using Access 2000 that sends out
e-mails automatically (or it used to). Recently I had to install servicepack
3 to correct some errors in the autoname correct feature. Now all my e-mails
request user input before they can go out (so much for automation). Anybody
know the workaround for this fine feature?
Click to expand...

What do you mean by "user input"?

Are you doing this via code or macro? If code, post the relevant portions of the code. If by macro, I can't really help.



Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com
 
I'm using the send object function in a macro to send a report snapshot to
specific individuals whenever the report is generated. This macro is inside
another macro that runs the query and opens the report for printing to be
inter-office mailed to people who don't have an intranet connection. It stays
in house but is routed thru an Exchange server in another state
 
Try using the code in a VBA procedure rather than in a macro. Also, try
retyping the code to be sure the syntax is correct.
 
I think it's just a security level in outlook (or whatever email software).
Just have a butchers in tools>options and there may be a "ask before automtic
sending from computer program" tick box or something like that.
 
Outlook 2000 doesn't have anything like that. Maybe it's something with
later versions, but I doubt it. As a test you could try e-mailing a report
snapshot as an attachment to an e-mail and see if you run into any
difficulties.

What is your actual code, and how are you running the code? Is it a macro,
or is it VBA? "Macro inside a macro that runs the query and opens the
report" is vague.
 
It is a pain in the ***. I believe that this "feature" was installed in the
Security patch to keep a program from sending email, something we wouldn't
want a worm program to do, however, MS hasn't seen fit to allow the owner of
a computer to override this for a specific program such as an Access macro.
I seem to recall a "workaround" in the KB but it didn't work.


Desperate!! said:
I think it's just a security level in outlook (or whatever email software).
Just have a butchers in tools>options and there may be a "ask before automtic
sending from computer program" tick box or something like that.
Try using the code in a VBA procedure rather than in a macro. Also, try
retyping the code to be sure the syntax is correct.
Click to expand...
[quoted text clipped - 17 lines]
Click to expand...
 
That could be. I was pretty sure it is not a user-controlled setting. I
ran into a similar sort of annoyance when I tried to send an e-mail link to
a database. I'll have to see if I have any better luck sending a customized
shortcut once I have implemented user-level security. I understand why an
administrator would want to lock some employees out of the chance to do
dangerous things to the network, but there is no reason for that to be a
hard-coded, inflexible mandate from MS.

jahoobob via AccessMonster.com said:
It is a pain in the ***. I believe that this "feature" was installed in
the
Security patch to keep a program from sending email, something we wouldn't
want a worm program to do, however, MS hasn't seen fit to allow the owner
of
a computer to override this for a specific program such as an Access
macro.
I seem to recall a "workaround" in the KB but it didn't work.


Desperate!! said:
I think it's just a security level in outlook (or whatever email
software).
Just have a butchers in tools>options and there may be a "ask before
automtic
sending from computer program" tick box or something like that.
Try using the code in a VBA procedure rather than in a macro. Also, try
retyping the code to be sure the syntax is correct.
Click to expand...
[quoted text clipped - 17 lines]
Anybody
know the workaround for this fine feature?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top