I have Windows 10 and Access 2016. I'm trying to get a database to run that works just fine on 64-bit Win7 and Access 2013. It's a split database, with the back end on MSSQL Server and the front end, of course, Access.

It seems that when ever this code runs it crashes Access 2016:

Private Sub Form_Open (Cancel As Integer)

Dim rstLogin As DAO.Recordset
DoCmd.Close acForm, "Login"

Set rstLogin = CurrentDb.OpenRecordset ("SELECT Role FROM Security WHERE User_Name = '" & strUserName & "';", dbOpenDynaset, dbSeeChanges)

If rstLogin.Fields ("Role").Value = "Admin" 
Then
Else
  Me.cmdManageUsers.Visible = False
End If

End IF

End Sub

What this does is make a command button visible on the form if the user is designated as and administrator.

The bug seems to be in the "Set rstLogin" line.

What has Microsoft changed that would cause Access to crash on this?

If I avoid opening this form, everything else in the database seems to work

---

Reply from Alex Hedley:

Did you change or add any References in Access vba window.
Access can be funny depending on whether DAO is before or after ADO.

One suggestion is I'd always have the Visibility of the admin buttons as hidden and only enable when the function has checked otherwise it may never get hidden if it fails and give users access they shouldn't have.