It seems Access 2010 is associating an 'input mask' or field type with a combo box when a form is opened, even though there is no Format setting on the control.
I have a form which has been running OK for years in Access 2003; it adds an item selected from an inventory listing to either an existing Sales Order or Purchase Order. For historic reasons Purchase orders are alphanumeric and Sales orders are numeric (long integer). The RowSource is set in the form's OnOpen event. Existing Sales Orders are listed in the combo box OK but when the form was used to select a Purchase order we got an error message "The value you entered is not valid for this field" - "..you may have entered text in a numeric field..."
On inspection I found that the 'Sales' order query had remained 'hard coded' as the RowSource in the Properties dialogue box. Simply removing this to leave a blank RowSource enabled the form to work 'normally' again.
I feel this is something new to Access 2010 so am writing about it in case other are stuck on it too.
I've hit another problem in my 2003 to 2010 migration which also involves a combo-box (displaying a wrong value). I can't resolve this and will write it as a separate thread after a few more tests.
S7
I have a form which has been running OK for years in Access 2003; it adds an item selected from an inventory listing to either an existing Sales Order or Purchase Order. For historic reasons Purchase orders are alphanumeric and Sales orders are numeric (long integer). The RowSource is set in the form's OnOpen event. Existing Sales Orders are listed in the combo box OK but when the form was used to select a Purchase order we got an error message "The value you entered is not valid for this field" - "..you may have entered text in a numeric field..."
On inspection I found that the 'Sales' order query had remained 'hard coded' as the RowSource in the Properties dialogue box. Simply removing this to leave a blank RowSource enabled the form to work 'normally' again.
I feel this is something new to Access 2010 so am writing about it in case other are stuck on it too.
I've hit another problem in my 2003 to 2010 migration which also involves a combo-box (displaying a wrong value). I can't resolve this and will write it as a separate thread after a few more tests.
S7
Comment