i have a user whose pc has been upgraded to access 2016 and they are the only person out of a group of 300 users who i beleive have now been upgrading and they have started experiencing this error.
I have tracked the error down to some code that i have for snoozing reminders, when access is trying to send a email via outlook.
i have wrote added the code to ignore this error for the time being, but would like to be able to try and understand why this is being logged as a error in 2016.
the code is :
I have tracked the error down to some code that i have for snoozing reminders, when access is trying to send a email via outlook.
i have wrote added the code to ignore this error for the time being, but would like to be able to try and understand why this is being logged as a error in 2016.
the code is :
Code:
Sub SnoozeReminders()
On Error GoTo handler
Dim olApp As Object
Dim objRems As Object
Dim objRem As Object
Set olApp = CreateObject("Outlook.Application")
Set objRems = olApp.Reminders
For Each objRem In objRems ' this is the highlighted code when i press debug.
If objRem.IsVisible = True Then
objRem.Snooze
End If
Next objRem
Exit Sub
handler:
If Err.Number = 424 Then
Resume Next
Else
Call LogError(Err.Number, Err.Description, "ErrSnoozeReminder", "")
Exit Sub
End If
End Sub