The value you entered isn't valid for this field!!!

[emptyC]

Hey all,

I have been beating my brains out trying to fix this problem but can't seem to! Here Goes!

I created a database in which it says:

Date | Test Number | Vehicle ID | Violation | Location

the format for date is short date, test number is number (interger), and the rest are text. I then proceded to make the form. I have text boxes for the first 3 and combo boxes for the last 2. The data for Violation and Location come from a different table (their columns are also text)

the data for violations looks like this

Violaton (text)
393.4
345.14R
396.485(a)
...... and so on

Locaton (text)
1L
1R
2L
2R
... and so on

when i cycle through each row of data in the form it gives me an error:
The value you have entered isn't valid for this field
blah blah blah blah

i keep messing around with stuff and i can't seem to fix it!! any ideas??

thanks a ton!

MT

 

[MStef]

What did you put in Date field ???

 

[emptyC]

I put the date as a short date. When the error comes up is specifically indicates (highlights it) its a problem with the last 2 entries (because of the combo box?)

 

[MStef]

Send a short example of your database, (access 2000 or 2002).

 

[khawar]

On which field you are using a combo box whether it is linked to some field in some other table

 

[emptyC]

Here is where the example is located... if you cycle back and forth through the 3 items you will see the errors. If you make a new entry it will be fine.

http://www.geocities.com/uebermenchens/Example.zip

Thanks for your help

MT

 

[Brianwarnock]

Why did you think it was the Date?

It is the violation codes that are causing the messages, eg 1L is ok but 1LR is not ; 393.4 is ok but nothing else is.

But I don't know the reason

Brian

 

[Tiro Cupidus]

You need to bind your combo boxes to your text column instead of your ID column since you are storing text values in your Violations table.

However, it would be better to store the IDs in your Violations table instead of text. If you do that, your combo boxes should be fine.

Edit:

Even better than that, though, would be to set up a many-to-many relationship. You could rename your Violations table to ViolationChecks and create two other tables named Violations and ViolationsToChecks, the latter being the one to match all the Violations up to the Checks.

 

[emptyC]

It had to be something dumb!! Thanks for your help i will bind the data... Sorry for the dumb mistake! The other 2 seemed too complicated at this moment if a revision is needed i will do it that way!

MT