The error would seem to indicate that there is a SQL statement, somewhere, that you haven't edited to reflect he Field name change. Understand that some SQL statements are generated by the Access Gnomes via various Wizards, and you may not even be aware that they exist. One example of this would be the creation of a Table-based Combobox, using the Wizard. You place the Control on the Form, the Wizard pops up, and you pick a Table or Query as a source, then you select Fields to include in the Combobox. If you then select the Combobox and go to Properties - Data and look at the RowSource Property, you'll see that Access has used a SQL statement to create a SELECT Query.
Depending on the size of your app, it could take a bit of time tracking all such occurrences down.
Or, of course, it could be an Access 'ghost!' These creatures do occasionally remain after changes like this have been made. They cure for this, I believe, is to import everything into a new, blank database.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007