Error 2105 from "Add New" Command Button

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rsmccli
    New Member
    • Jan 2008
    • 52

    Error 2105 from "Add New" Command Button

    Using AC2002

    Hello. I am working with an existing DB that has "Add New" command buttons on two forms.

    When I, an Admin, click the buttons, they work properly, and a new, blank form is created, ready for data entry.

    When one of my users from the "Update Data" workgroup clicks the button, they get an "Error 2105: You can't go to the specified record" error, and no new row is created. Each of these are just supposed to add a new row in their respective tables.

    Could this just be a security issue; I'm assuming so because Admins can use the button. However, I changed the table permissions to allow Open/Run, Read, Update, Insert, and Delete on all tables and am still having issues. Here is the code behind one of the buttons without errorhandling
    Code:
    Private Sub cmdAddRec_Click()
    On Error GoTo ErrorHandler
    
    ' add new record
      Me.AllowAdditions = True
      DoCmd.GoToRecord , , acNewRec
      
    ' set focus to first data entry field
      Me.Plant.SetFocus
      
    End Sub

    Any help is appreciated.
  • rsmccli
    New Member
    • Jan 2008
    • 52

    #2
    Also notable is that it appears that the new record is being made, because the first time an "update user" clicks the button, there is no error, only the second and third, etc. button clicks produce the error. They are just not able to navigate to the new record using the navigation buttons, as "admins" can.

    Thanks again for looking.

    Comment

    • rsmccli
      New Member
      • Jan 2008
      • 52

      #3
      bump Update Data users can manually create a new field in the table... Allow Additions property is set to "yes" even though this is taken care of in code also...

      Comment

      • Ademola Adebayo
        New Member
        • Sep 2010
        • 1

        #4
        How did you resolve this issue, because I am having the exact same problem

        Comment

        Working...