Email (SendObject) works for some and not others.

"Ann" wrote in message

We are using 2002 and it has SP3 but the message said it was a
problem with 2000 and above.

I think Roger was mistaken in that. I'm not aware of any ongoing
problems with SendObject after Access 2000 SP3. SP3 for Office 2002 is
a different update. That is, I'm not aware of any problems except the
confirmation prompts required by the e-mail security update. But my
understanding was that your real problem was that SendObject sometimes
simply didn't operate at all. That's the problem I've been talking
about.

We are already using MAPI. It said that was the only way we could use
Outlook with our applications and the macro is correct. I was hoping
it would be as simple as a setting in Outlook that needed to be
changed. Thanks for your help.

Now I'm confused. If you're using the built-in SendObject method
(DoCmd.SendObject) then you're not using MAPI (except in that Access may
be using MAPI behind the scenes).

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

am using SendObject in a macro. The Client is on our desktop, the rest is
on a network server. Support said sending mail automatically doesn't work
without MAPI but we were setup properly and I shouldn't have a problem. And
yes, you are correct, my real problem is that SendObject sometimes simply
doesn't operate at all. Out of seven people only one person's doesn't work.
I do this in other databases and this is the first time I have had a problem.
In fact the person it doesn't work for used it in a different database all
last year without a problem. The only difference is that now it is sending
to multiple recipients instead of just one. I'm extremely confused and have
no idea where to look. I appreciate your help.

"Dirk Goldgar" wrote:

"Ann" wrote in message

We are using 2002 and it has SP3 but the message said it was a
problem with 2000 and above.

I think Roger was mistaken in that. I'm not aware of any ongoing
problems with SendObject after Access 2000 SP3. SP3 for Office 2002 is
a different update. That is, I'm not aware of any problems except the
confirmation prompts required by the e-mail security update. But my
understanding was that your real problem was that SendObject sometimes
simply didn't operate at all. That's the problem I've been talking
about.

We are already using MAPI. It said that was the only way we could use
Outlook with our applications and the macro is correct. I was hoping
it would be as simple as a setting in Outlook that needed to be
changed. Thanks for your help.

Now I'm confused. If you're using the built-in SendObject method
(DoCmd.SendObject) then you're not using MAPI (except in that Access may
be using MAPI behind the scenes).

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

"Ann" wrote in message

am using SendObject in a macro. The Client is on our desktop, the
rest is on a network server. Support said sending mail automatically
doesn't work without MAPI but we were setup properly and I shouldn't
have a problem. And yes, you are correct, my real problem is that
SendObject sometimes simply doesn't operate at all. Out of seven
people only one person's doesn't work. I do this in other databases
and this is the first time I have had a problem. In fact the person
it doesn't work for used it in a different database all last year
without a problem. The only difference is that now it is sending to
multiple recipients instead of just one. I'm extremely confused and
have no idea where to look. I appreciate your help.

I'm rather perplaxed, too, but let's see if we can figure out what's
wrong. Please clarify: when you say you are using SendObject "in a
macro", do you mean a real macro, as shown on the Macros tab of the
database window, or are you referring to a VBA procedure?

For the one person for whom it doesn't work, does it *never* work, or
sometimes yes, sometimes no?

Is there VBA code involved at all, or is it all macros?

Have you checked for a missing or broken reference on the one PC where
it's failing, according to Doug Steele's instructions posted he

http://www.accessmvp.com/djsteele/Ac...nceErrors.html

?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

It's a macro on the macros tab of the database window, no VBA procedure.
There are 11 conditions. One for each user, ex. ([txtUserId] like
"AMV5520"), if the condition is met do the SendObject. This sends to
everyone but the user who logged the problem and it inserts the log no. into
the text of the message that gets sent to the other 10 users. For this
person it never works in this database, but SendObject has worked for her in
a completely different one we used last year. The one from last year only
had 1 recipient and this one has 10.

I hadn't checked the references but just did and none are marked as "Missing".

I'm not a programmer but would it be better to use a VBA procedure instead?
I did come across some and can figure it out enough if I have to change
something.

"Dirk Goldgar" wrote:

"Ann" wrote in message

am using SendObject in a macro. The Client is on our desktop, the
rest is on a network server. Support said sending mail automatically
doesn't work without MAPI but we were setup properly and I shouldn't
have a problem. And yes, you are correct, my real problem is that
SendObject sometimes simply doesn't operate at all. Out of seven
people only one person's doesn't work. I do this in other databases
and this is the first time I have had a problem. In fact the person
it doesn't work for used it in a different database all last year
without a problem. The only difference is that now it is sending to
multiple recipients instead of just one. I'm extremely confused and
have no idea where to look. I appreciate your help.

I'm rather perplaxed, too, but let's see if we can figure out what's
wrong. Please clarify: when you say you are using SendObject "in a
macro", do you mean a real macro, as shown on the Macros tab of the
database window, or are you referring to a VBA procedure?

For the one person for whom it doesn't work, does it *never* work, or
sometimes yes, sometimes no?

Is there VBA code involved at all, or is it all macros?

Have you checked for a missing or broken reference on the one PC where
it's failing, according to Doug Steele's instructions posted he

http://www.accessmvp.com/djsteele/Ac...nceErrors.html

?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

"Ann" wrote in message

It's a macro on the macros tab of the database window, no VBA
procedure. There are 11 conditions. One for each user, ex.
([txtUserId] like "AMV5520"), if the condition is met do the
SendObject. This sends to everyone but the user who logged the
problem and it inserts the log no. into the text of the message that
gets sent to the other 10 users. For this person it never works in
this database, but SendObject has worked for her in a completely
different one we used last year. The one from last year only had 1
recipient and this one has 10.

I'd love to blame the macro, but if the same macro works for everybody
else, that's hard to do.

I'm not a programmer but would it be better to use a VBA procedure
instead?
I did come across some and can figure it out enough if I have to
change something.

In general, VBA code is more powerful, more flexible, and easier to
debug. I generally recommend using it instead of macros if you feel up
to it, but not everyone is a programmer. If you want to give it a try,
I'll be glad to help you. If you want me to, post back with the details
of every action in the macro. I'd need that anyway if I were to try and
debug the macro.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

I would appreciate your help...thank you very much.

Here is the macro information.
Name: Email,
Condition: ([txtUserId] Like "AMV5520") one for each user with their User Id.
SendObject
To property:

Subject: Problem Logged
Message Text: ="Please check Problem Log Number" & " " &
[lngProblemResolutionId] & "."
Edit Message: No

"Dirk Goldgar" wrote:

"Ann" wrote in message

It's a macro on the macros tab of the database window, no VBA
procedure. There are 11 conditions. One for each user, ex.
([txtUserId] like "AMV5520"), if the condition is met do the
SendObject. This sends to everyone but the user who logged the
problem and it inserts the log no. into the text of the message that
gets sent to the other 10 users. For this person it never works in
this database, but SendObject has worked for her in a completely
different one we used last year. The one from last year only had 1
recipient and this one has 10.

I'd love to blame the macro, but if the same macro works for everybody
else, that's hard to do.

I'm not a programmer but would it be better to use a VBA procedure
instead?
I did come across some and can figure it out enough if I have to
change something.

In general, VBA code is more powerful, more flexible, and easier to
debug. I generally recommend using it instead of macros if you feel up
to it, but not everyone is a programmer. If you want to give it a try,
I'll be glad to help you. If you want me to, post back with the details
of every action in the macro. I'd need that anyway if I were to try and
debug the macro.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)