Changing Name of Key Field Breaks List Box Look Up Control in Form

[ccook13]

Using Access in Office 365, I changed the name of the key field in a table to something more intuitive. While the name change propagated through queries and forms as expected, the change broke an unbound list box control used to look up records in a form. Despite diagnosing the problem I was unable to find a solution. As a work around I created a new unbound list box and using the list box wizard in Access set up the control to look up records in the form. The control works as expected and like the old control used to work.

When I compare the properties and SQL code of the old and new list boxes everything appears identical. Can someone explain the source of my problem? Thanks for your help!!

 

[welshgasman]

Possible because it was unbound?
All you needed to do was change the name in the rowsource to match the new name?

 

[ccook13]

Possible because it was unbound?
All you needed to do was change the name in the rowsource to match the new name?

This did occur to me but the field name in the list box query did update to the new field name (ie, ID to Project_ID).

 

[Micron]

You could have copied the listbox rowsource and dumped it into a new query and tried to run it from sql view. If it balks, the offending part is often highlighted or the message about what's wrong is usually clear. If it ran ok, then likely the control was corrupt. You could also post both rowsource sql statements and maybe someone could spot something amiss.