Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

using navigation buttons triggers invalid value entered msg 1

Status
Not open for further replies.

pondside

Programmer
Jul 6, 2003
11
US
I have a tabbed form that has suddenly developed a new glitch when I use the Access-provided navigation buttons. Whether I move forwards or backwards by record using the buttons, I get a message:

"The value you entered is not valid for this field."

The subtext of the message box continues:


"For example, you may have entered text in a numeric field or a number that is larger than the field size permits"

I am not entering numbers or text, simply navigating. What might be causing this? I need some clue about where to look.
 
It is possible that your form and or database may have become corrupted. First, try creating a new form. If that doesn't work, make a new, empty database and import everything from the old into it.

REMEMBER - before doing anything, make a copy and work from it.

Good Luck !!

An investment in knowledge always pays the best dividends.
by Benjamin Franklin
 
MPH1: Thanks! I'll try what you suggest, and let you know the outcome.... Pondside
 
MPH1:
Your clue about the form corruption led me to the culprit. My main form had several subforms, so creating a new form was not a viable option. However, your suggestion of new imports was an excellent idea.

Fortunately, I make copies of the database up to 5 or 6 times a day, so I was able to backtrack very precisely to where the error crept in, use the immediately prevous version as a temporary base, and start importing subforms from the most recent copy. It turned out to be a subform that was invalid.

The cautionary tale: I had a combo box in that subform and my vba code connected to the combo box was stashing items from the wrong column of the box into the underlying table field. Since I was only making isolated updates as part of a testing effort, and not subsequently using the navigation buttons in the vicinity of the errors, much time past before I stumbled on the error.

So the error message was correct, but sadly gave no clue as to which field on which subform was the villain.

Many thanks again, for pointing out a useful approach to finding the problem.
 
I am really glad that everyting worked out. Actually, what you describe happened to me several years ago and I got burnt.

An investment in knowledge always pays the best dividends.
by Benjamin Franklin
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top