Run-Time Error 2109 - Microsoft Access Forum


	Back to Access Forum Comments List

Upload Images @Reply Bookmark Link Email Next Unseen

Run-Time Error 2109

Chris Whittingham

4 years ago

Richard Rost was very helpful with the following code to help me remove the filter and stay on current record on a From.

Private Sub ShowAllGoBack_Click()

    Dim ID As Long
    ID = PersonID
    Me.FilterOn = False
    DoCmd.GoToControl "PersonID"
    DoCmd.FindRecord ID

End Sub

It brilliant and works fine on one database but when using it in another databace Form, using exactly the same back-end tables I get a run-time error '2109': saying There is no field named PersonID in the current record.
Any feedback from the forum would be very much appreciated.

	Chris Whittingham OP @Reply 4 years ago

	Scott Axton @Reply 4 years ago
Chris - Any time you get an error - Especially like above ^^ First: Do you have a *PersonID* field on your new form? Second: (This is the most common issue) Check your spelling. In the error you are receiving above, Access is saying, "HEY, you told me to do something with 'PersonID', but I can't find a field with that name."

	Chris Whittingham OP @Reply 4 years ago
Thanks Scott. I defiantly do have a PersonID field on my Form, that's why I cant understand why I get the error.

	Scott Axton @Reply 4 years ago
Please post a screen capture or two in design mode of your form and properties of the PersonID in particular.

	Chris Whittingham OP @Reply 4 years ago
Problem solved. Spoke to a friend who advised me to go into design view, remove the PersonID field from the Form, save and close the form. Reopen the form in design view and add the PersonID field, save and close. Works fine now no run-time error '2109' popping up when I hit the refresh and stay on current record button.

	Scott Axton @Reply 4 years ago
Great. Thanks for letting us know.

	Chris Whittingham OP @Reply 4 years ago
Thanks for your time Scott, feedback much appreciated.

	Richard Rost @Reply 4 years ago
I'll bet the TEXT BOX control wasn't named PersonID. It was probably Text10 or something like that, just BOUND TO the PersonID field. I see this a lot.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Access Forum.

Next Unseen

New Feature: Comment Live View