none
After Upgrading from MS Access 2013 to MS Access 2016 "SendObkect' isn't available RRS feed

  • Question

  • Our division upgraded from MS Access 2013 to MS Access 2016. After Upgrading from MS Access 2013 to MS Access 2016 all users are receiving the following message "The command or action "SendObject' isn't available now." We are using GroupWise Program Release 12.0.0.2.

    I have searched high and low and this seems to be a definite occurring problem for many and in alarming cases as unresolved. We heavily rely on the <g class="gr_ gr_10 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="10" id="10">db</g> for operations and client services.  Currently, it is all impaired as result of the upgrade with no solution.  <g class="gr_ gr_13 gr-alert gr_gramm gr_inline_cards gr_run_anim Punctuation only-ins replaceWithoutSep" data-gr-id="13" id="13">Please</g> could you assist?


    • Edited by MvdBergh Friday, March 9, 2018 11:37 AM
    Friday, March 9, 2018 11:35 AM

Answers

  • Good news.

    It has been discovered that the version released was faulty. We have uninstalled the current MS Office 2016 package and reinstalled it with a newer release of MS Office 2016.  This solved all the problems.

    Thank you all for your inputs.  I will, however, adjust my programming to avoid using SendObject in case a future recurrence would appear.

    Thanking you all.




    • Marked as answer by MvdBergh Tuesday, March 13, 2018 11:25 AM
    Tuesday, March 13, 2018 11:25 AM

All replies

  • What is your build number?

    Have you tried updating or reverting to a prior build to see if it an issue with your specific build number.

    Can you post your code for us to review?


    Daniel Pineault, 2010-2017 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Friday, March 9, 2018 12:41 PM
  • The title says SendObkect; is that a spelling error?


    Sam Hobbs
    SimpleSamples.Info

    Friday, March 9, 2018 9:23 PM
  • Hi MvdBergh,

    I try to make a test with Access 2016 version below.

    Code:

    Sub demo()
    DoCmd.SendObject acSendTable, "product", acFormatXLS, _
        "Nancy Davolio; Andrew Fuller", "Joan Weber", , _
        "Current Spreadsheet of Employees", , True
    End Sub
    

    Output:

    You can see that on my side it is working without any issue.

    To avoid this issue , You can try to create a mail using Outlook with the code below.

    Public Function CreateEmailWithOutlook( _
        MessageTo As String, _
        Subject As String, _
        MessageBody As String)
    
        ' Define app variable and get Outlook using the "New" keyword
        Dim olApp As New Outlook.Application
        Dim olMailItem As Outlook.MailItem  ' An Outlook Mail item
    
        ' Create a new email object
        Set olMailItem = olApp.CreateItem(olMailItem)
    
        ' Add the To/Subject/Body to the message and display the message
        With olMailItem
            .To = MessageTo
            .Subject = Subject
            .Body = MessageBody
            .Display    ' To show the email message to the user
        End With
    
        ' Release all object variables
        Set olMailItem = Nothing
        Set olApp = Nothing
    
    End Function

    You can replace the Send Object code with the code above to send your object. It will solve your issue.

    Further, I suggest you to check for any pending Windows / Office related updates and if it is available then try to install it and again try to reproduce the issue.

    Reference:

    DoCmd.SendObject Method (Access)

    Regards

    Deepak


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, March 12, 2018 1:56 AM
    Moderator
  • Good all.

    Thank you for the feedback.

    The 64-bit version of Office 2016 does not display a build number nor is an update functionality available as it is being administered by my intuition’s IT department.  I have requested the build number to made available in order to post it here as well as to allow for an update check.

    The database has various forms from where emails can <g class="gr_ gr_70 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar multiReplace" data-gr-id="70" id="70">be send</g>; however, none of these <g class="gr_ gr_87 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar multiReplace" data-gr-id="87" id="87">are</g> now functional.  The same error message appears at every one.

    Here is the code of one of these.  A macro is called via VBA.  I have even converted the Macro to VBA without any success. Herewith the original code and macro.

     

    Private Sub EmailAcceptance_Click()

    Dim FileNaam As String

     

    If IsNull(Admin) Then

        Cancel = True

        MsgBox ("Please select an Administrative officer.")

        Admin.SetFocus

        GoTo 1

    End If

     

    If IsNull(Stoorroete) Then

        Cancel = True

        MsgBox ("Please enter location to save documents.")

        Stoorroete.SetFocus

        GoTo 1

    End If

     

    'BepaalVerslag

    If txtTaal = "Afr" Then

    txtVerslag = "WelkomPROGA"

    txtHeader = "AANSOEK OM TOELATING " + "- " + txtProgAfk

    Else

    txtVerslag = "WelkomPROG"

    txtHeader = "APPLICATION FOR ADMISSION " + "- " + txtProgAfk

    End If

     

    DoCmd.Save

    DoCmd.OpenReport txtVerslag, acViewPreview, , , acHidden

     

    txtSaamNaam.Value = lstEposEenv.Column(0)

    txtSID = lstEposEenv.Column(3)

    'txtTaal.Value = lstEposEenv.Column(4)

     

    FileNaam = Stoorroete.Value + txtVerslag.Value + " " + txtJaar + " - " + txtProgAfk + " - " + txtSaamNaam.Value + ".pdf"

    DoCmd.RunMacro ("E-pos Individuele Boodskap - PROG")

     

    If chkStoor = 1 Then

        DoCmd.OutputTo acOutputReport, txtVerslag, "PDFFormat(*.pdf)", FileNaam, False, "", 0, acExportQualityPrint

    Else

    End If

     

    1: End Sub

     The Macro

     

     

    OnError


     

    Go to  Next


     

    Macro Name

     

    EMailDatabaseObject

    Object Iype  Keport Object Name =[txtVerslag]

    Output Format   PDF Format (*.pdf)

     

    To  =[txtEpos]

     

    Cc

     

    Bee

     

    Subject =[txtHeader] Message Text =[boodskapJ Edit Message  Yes

    Template File

     

    If  [MacroError].[Number]<>O ThenMessageBox

    Message  =[MacroError].[Description]

     

    Beep  Yes Type   None Title

    End If

    CloseWindow

    Object Type  Report Object Name   =[txtVerslag]

    Save Yes


    Since we are using GroupWise, I’ll investigate a similar method for GW as you have explained with Outlook (Thaks a million).  I’ll keep you posted.

    Let's hold thumbs.


    • Edited by MvdBergh Monday, March 12, 2018 6:42 AM
    Monday, March 12, 2018 6:39 AM
  • Hi MvdBergh,

    I try to check your code and find that there is no any "DoCmd.SendObject " line in your code.

    If you only posted the half code then I suggest you to post a full code.

    I also suggest you to post your code in code block.

    Currently, It is difficult to view and understand your code.

    Further, It is possible that Administrator has applied any group policy and because of that reason "DoCmd.SendObject " is not working.

    So you can also confirm this with your administrator.

    How administrators can use Office policy templates together with the Group Policy settings of Windows

    Regards

    Deepak


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, March 12, 2018 7:53 AM
    Moderator
  • Good news.

    It has been discovered that the version released was faulty. We have uninstalled the current MS Office 2016 package and reinstalled it with a newer release of MS Office 2016.  This solved all the problems.

    Thank you all for your inputs.  I will, however, adjust my programming to avoid using SendObject in case a future recurrence would appear.

    Thanking you all.




    • Marked as answer by MvdBergh Tuesday, March 13, 2018 11:25 AM
    Tuesday, March 13, 2018 11:25 AM