Results 1 to 5 of 5
  1. #1
    cebrower is offline Competent Performer
    Windows 7 64bit Access 2010 32bit
    Join Date
    Mar 2018
    Location
    Spring Lake, MI
    Posts
    110

    Value not valid for this field (run-time error '2113')


    I have a form named frmConfirmEdit with a text field named ConfirmationNumber. In the On Load event of frmConfirmEdit the confirmation number is written to an unbound field on a different form so code in other forms, reports, etc. can refer to it. This has worked fine for years. Today, when I open frmConfirmEdit I get the message "The value you entered is not valid for this field. Run-time error 2113". There are 200 records in the record source for frmConfirmEdit. I only get this error for one of those records. The form opens properly for any of the other records. I've run Compact and Repair on both the front end and the back end databases, I've decompiled and recompiled the front end, I've manually re-typed the value in the table, and I've deleted and recreated the record. Still get the error. Any suggestions?

  2. #2
    orange's Avatar
    orange is online now Moderator
    Windows 10 Access 2010 32bit
    Join Date
    Sep 2009
    Location
    Ottawa, Ontario, Canada; West Palm Beach FL
    Posts
    16,726
    Where is the backend Access, sqlserver...)?

    I found a thread that discusses that 2113 error and CajunCenturion has an answer near the end of the thread.
    Don't know if it is similar to your situation, but you may get some insight from that thread.

  3. #3
    cebrower is offline Competent Performer
    Windows 7 64bit Access 2010 32bit
    Join Date
    Mar 2018
    Location
    Spring Lake, MI
    Posts
    110
    Problem solved: The record source query for frmConfirmEdit has a field in tblConfirm named [TaxCode] that links to tblTaxInfo!TaxCode, but it was null in tblConfirm so no record was returned. The lesson is that the error message does not always lead you to the actual problem.

  4. #4
    orange's Avatar
    orange is online now Moderator
    Windows 10 Access 2010 32bit
    Join Date
    Sep 2009
    Location
    Ottawa, Ontario, Canada; West Palm Beach FL
    Posts
    16,726
    Good stuff. Thanks for posting your findings.

  5. #5
    Missinglinq's Avatar
    Missinglinq is offline VIP
    Windows 7 64bit Access 2007
    Join Date
    May 2012
    Location
    Richmond (Virginia, not North Yorkshire!)
    Posts
    3,018
    Quote Originally Posted by cebrower View Post

    ...The lesson is that the error message does not always lead you to the actual problem...
    Sadly, Access' error messaging system is not the best in the world! Also, when you break on an error, the line hi-lited is not always the line causing the problem...it is often the line preceding that line!

    Glad you got it figured out!

    Linq ;0)>
    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 5
    Last Post: 01-13-2017, 02:20 AM
  2. Replies: 4
    Last Post: 02-17-2016, 01:53 PM
  3. Replies: 4
    Last Post: 06-04-2015, 01:07 PM
  4. 2113 Error happening from Access 2003 to 2010
    By johnnyflames in forum Forms
    Replies: 5
    Last Post: 06-08-2012, 01:42 PM
  5. Replies: 1
    Last Post: 07-21-2009, 03:01 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums