Form asking for number but table is text

[School Boy Error]

Hi,



I have designed a database where there are several forms that pull information from the back end table and one that inputs data. I have changed the table to allow "Year Group" to be text because now but on two forms it is saying "R" isn't an allowed value. These are two query forms not data entry if that makes a difference but the data entry form allows an R to be put in the query forms come up with an error when I try and run with "R" in.

I have attached the front end file and the two affected tables are frm_Report Builder and frm_Analysis Builder

Thank you! Behaviour Log v2.1.zip

[School Boy Error]

Sorry, I've added the table to the zip file now.

[John_G]

Hi -

In your two forms where you select the year group from a combo box, there is a property for the combo box control called "Inherit Value List"

Change that property to "No"

I really don't know why this worked, because I'm not familiar with the Inherit Value List property; but it looked like a good candidate to try to solve the problem!

[Missinglinq]

...I really don't know why this worked...I'm not familiar with the Inherit Value List property...

My guess would be that it wasn't the Inherit Value List property, per se, but that changing any of the properties of the Combobox would have worked. When the Combobox was originally created, the Control Source Field was either Numeric or DateTime, and as far as the Combobox was concerned, remained so, even after the Datatype for the Field was changed in the TableDef. I suspect that by changing a property, Access 'resets' all of the internal works and now recognizes it as Text. Simply recreating the Combobox, after changing the Datatype, would probably have worked, as well.

Still an interesting phenomenon!

Linq ;0)>

[John_G]

Hi Linq-

You are probably right. If I change the Inherent Value List back to "Yes", I don't get the error.

I recall that I had much the same thing happen some time ago - when I added a field to a table or query, the form using that table did not see the new field until I reset the form's recordsource.

Not really a bug, but not a particularly good implementation either, IMO.

Cheers!