Email from access form transfered to different version OS

[WAVP375]

I have developed an application where I email a document via a form. I have done my development on Windows 10 system with Access and outlook level 2016. I am attempting to implement it on a corporate system running Access and Outlook 2010. When I execute the first code I get and error saying 'Can't find Project or library'. The reference list in tools shows a 'Missing Microsoft Outlook 16.0 Object library'. This library does not exist in the reference list and I did not find this object for any other level such as 'Microsoft Outlook 10.0. There must be a way around this?

[Micron]

Older or newer versions of references have to be available to all generations of a db or Office install. In other words, you set a reference to 16.0 but it's not likely available to a computer running an older Office version. The older one is more likely available to the newer version in a corporate environment. You'll have to figure out where they are and make them available, or you could try late binding in your code.

[WAVP375]

I have no idea where to look for them or how to make them available. Nor do I know anything about late binding.

Thanks

[Micron]

You'll have to decide on whether to make the new references available to the old, or vice-versa. Or have 2 apps, one for each group of users, in which case you don't have to do any of the following.

Open the db. press Alt+F11. In the vb editor, choose Tools>References. Select a reference from the list and the path it thinks is correct will be displayed in the References dialog form near the bottom. Most likely you won't be able to see the entire path (and the form is not expandable) but it should give you an idea of where to start a file search for that file. The file would have to be distributed along with the front end of your db. That's about the best I can suggest, other than Googling late binding.

[WAVP375]

I am out of my league here. It would help to see sample code for the early binding.

If I were to solve this with the two application method how much of the application must be redeveloped on the host system?

Thanks

[Bulzie]

Can you save the db in Access 2010? Not sure if that would resolve anything. As Micron said, try to find that "Microsoft Outlook 16.0 Object library" file on your harddrive and then copy it to a network folder or the local folder where the program will reside. And in your program, uncheck the Outlook 16 reference and add the one that is in that local folder.

[Micron]

I am out of my league here. What part of my previous post do you need help with?

Late binding means that an object is declared as "Object" for example, instead of being more specific about the type of object. This method requires no reference to a type library and can be used if the object supports late binding:
Dim oExcel As Object
Set oExcel = CreateObject("Excel.Application")

Early binding requires a type library (reference set in vb editor Tools > References):
Dim oExcel As Excel.Application
Set oExcel = CreateObject("Excel.Application")

The following is based on not having seen any of your code.
Early binding is likely what your code uses. I'm fairly certain that code using late binding will still cause your error if the library reference is checked but cannot be found, so you would have to uncheck it to prevent the error message if using late binding. Late binding causes code to run slower and does not provide Intellisense (the automatic completion of form/report object control references or the syntax and parameters for built in functions) when you are typing. You'll have to weigh that against the upside of late binding.

Your easiest solution is probably to alter only the procedures that use Outlook so that you use late binding. Know also that since you developed in 2016 and I gather that older Access versions will be using this db, you might have used 2016 features that would cause issues on a pc using Access 2007 but problems haven't arisen yet.

I'm using Office 12 at home, so any Access code invoking the Outlook application requires a reference to Microsoft Outlook 12 type library which the References dialog box (in the aforementioned vb editor) shows as being located at
C:\Program Files\Microsoft Office\Office12\MSOUTL.OLB
I don't recall ever having this problem because at work, everyone was always on the same version of Office so the references only had to be updated. I don't see why finding and including the type library you need wouldn't work if it was part of your distribution package. Keep a backup copy of your working db before you go altering code.

[WAVP375]

Following is the code I am using. It works well in Access 2016.
Private Sub BtnEmail_Click()

'Check for email address
If IsNull([EmailAddress]) Then
MsgBox "Enter Email Address"
Me.EmailAddress.SetFocus
Else: GoTo Continue
End If
Exit Sub

'Send email
Continue:
Dim FileName As String
Dim FilePath As String
Dim oOutlook As Outlook.Application
Dim oEmailItem As MailItem


FileName = Me.DocumentTitle
FilePath = Me.ImagePath


If oOutlook Is Nothing Then
Set oOutlook = New Outlook.Application
End If

Set oEmailItem = oOutlook.CreateItem(olMailItem)

With oEmailItem
.To = Me.EmailAddress
.Subject = "Document From Greene Memorial Archive System"

.Attachments.Add FilePath
.Send
End With

Set oEmail = Nothing
Set oOutlook = Nothing

MsgBox "Email has been sent to " & Me.EmailAddress
DoCmd.Close acForm, "frmSearch"
DoCmd.Close
DoCmd.OpenForm "frmMenu"
End Sub

What code needs to be changed to use late binding. I am still trying to get my mind around the whole concept..
I appreciate your patience and help

[Bulzie]

Did you try removing(uncheck) that reference to MS Outlook, save and compile the code, does it give an error?

[Micron]

As I mentioned, late binding will require you to remove the missing reference. Yes, it will generate an error if the reference cannot be found on a computer AND you are using early binding, which you are. In future, please use code tags and indentation to make code easier to read. I took the liberty of re-writing your code in a way that I think will work. Plus I introduced some of my own preferences, such as grouping declarations and added an error handler. You'll notice I removed the Else and GoTo as such direction is not required if you grasp the flow as written.

Private Sub BtnEmail_Click()
Dim FileName As String
Dim FilePath As String
Dim oOutlook As Object
Dim oEmailItem As Object

On Error GoTo errHandler
FileName = Me.DocumentTitle
FilePath = Me.ImagePath

'Check for email address
If IsNull([EmailAddress]) Then
 MsgBox "Enter Email Address"
 Me.EmailAddress.SetFocus
 Exit Sub
End If

'Send email
If oOutlook Is Nothing Then 
 Set oOutlook = New Outlook.Application
 Set oEmailItem = oOutlook.CreateItem(olMailItem)
End If

With oEmailItem
 .To = Me.EmailAddress
 .Subject = "Document From Greene Memorial Archive System"
 .Attachments.Add FilePath
 .Send
End With

MsgBox "Email has been sent to " & Me.EmailAddress
DoCmd.Close acForm, "frmSearch"
DoCmd.OpenForm "frmMenu"
DoCmd.Close
Exit Sub

exitHere:
Set oEmailItem = Nothing 'OEmail was not a declared object or variable
Set oOutlook = Nothing

errHandler:
MsgBox "Error " & Err.Number & ": " & Err.Description
Resume exitHere 'if you want to close forms regardless of a run time error, you can move the
'close commands to the exitHere block. Note that if you mis-spell or rename form, a continuous 
'error loop will occur unless you alter the errHandler block to trap for that particular error.

End Sub

[WAVP375]

I'll work on it

Thanks

[Micron]

BTW, when you get this working you are likely going to get the security prompt and will have to click ok to send each email. Not sure if you're aware of that.