Share via

'SendObject' isn't available now

Anonymous
2010-09-16T01:30:44+00:00

Have a Db in AC2000 that has worked for years.  Works fine on a PC running AC2007 and saved as a AC2000 db.  When copied to a PC that only has AC2000 I get the error "The command or action  'sendObject' isn't available now"  when using VBA to send an email.

HELP

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2010-09-17T00:10:34+00:00

Fixed the problem myself.  After trying another Access DB on the problem PC with the same error msg I loaded the install CD and ran the Office repair option.  Evidently Access was corrupt.

Was this answer helpful?

0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2010-09-27T17:30:16+00:00

    Steve Staab wrote in

    news:*** Email address is removed for privacy ***

    m:

    is it possible the Send/Receive button in Outlook invokes a different 'SEND' function/routine than the one invoked by the 'SendObject' VBA command?¶ÿ I wouldn't think that

    is the case but ....

    It's absolutely different. VBA SendObect uses your computer's MAPI

    settings to choose the default email client (which doesn't have to

    be Outlook). Outlook uses its internal commands to send the email,

    which use MAPI but don't use your computer's default MAPI settings

    (that is, Outlook can send email even if Outlook is not set as your

    default MAPI client).

    The way MAPI works is obscure and problematic, and the interaction

    with Outlook and other email clients is complex and prone to error

    and failure. Running the Office repair process obviously healed

    whatever had gone wrong in your computer's MAPI settings. Whether

    this will permanently remain "fixed" is another question, and one

    reason why I'd tend to use direct automation of Outlook in

    preference to SendObject if Outlook was known to be the email client

    of choice.


    David W. Fenton                  http://www.dfenton.com/ contact via website only     http://www.dfenton.com/DFA/

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-09-27T03:44:01+00:00

    Tony,

    Since Outlook seemed to be working OK in that we could Send AND Receive emails normaly from Outlook for the FEW DAYS while I was working on this problem my vote would be that Outlook was NOT the problem.

    If Outlook appears to be functioning OK but 2 Access DBs display the same error message then it seems to point to Access being corrupt on that one PC. 

    Or, on second thought,  is it possible the Send/Receive button in Outlook invokes a different 'SEND' function/routine than the one invoked by the 'SendObject' VBA command?  I wouldn't think that is the case but ....

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-09-26T23:36:32+00:00

    Steve Staab wrote:

    Fixed the problem myself.  After trying another Access DB on the problem PC with the same error msg I loaded the install CD and ran the Office repair option.  Evidently Access was corrupt. 

    Or it may have been that Oulook wsa corrupt if Outlook is the default email client.

    Tony

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-09-16T02:34:28+00:00

    What eMail program is on the old machine?  And what one is on the new machine?


    -- Gina Whipp 2010 Microsoft MVP (Access) Please post all replies to the forum where everyone can benefit.

    Was this answer helpful?

    0 comments No comments