Resolved (Autocorrect) Has anyone seen this bug...
I've been working with MS Access for many years now, and recently migrated to 2002 Developer's edition on a Win2k workstation.
I habitually use the wizard to develop a basic form (or report), and then tweak the result until I'm happy. The wizard binds the source fields from the query/table to text boxes with labels successfully. When I then "tweak" a field, such as an address, I will change the control source (e.g., combine the City, State, and Zip fields into a single concatenated and formatted field via a formula) and the name by prefixing the default value with an "s". The problem I've encountered is that if I run the form from this "developing" version the form generates a "#Name" error in the field that I've tweaked; I've discovered that I really haven't really made a mistake, because I can save and close the form and then immediately reopen it in run mode and get the right result to appear.
Has anyone else encountered this situation? I spend some time doubting what I've written or verifying my context, and it's starting to get very annoying, since I haven't encountered this in previos editions.
Thanks.
Found the problem to be related to the Autocorrect setting, and the manner in which Access assigns the "name" to a field you place on a form or report. With autocorrect turned "on", a change to the "name" value autocorrects to the formula, which leads to the #Name error. I haven't found a good workaround, as there are instances when you want autocorrect on and others where you want it off.
I've been working with MS Access for many years now, and recently migrated to 2002 Developer's edition on a Win2k workstation.
I habitually use the wizard to develop a basic form (or report), and then tweak the result until I'm happy. The wizard binds the source fields from the query/table to text boxes with labels successfully. When I then "tweak" a field, such as an address, I will change the control source (e.g., combine the City, State, and Zip fields into a single concatenated and formatted field via a formula) and the name by prefixing the default value with an "s". The problem I've encountered is that if I run the form from this "developing" version the form generates a "#Name" error in the field that I've tweaked; I've discovered that I really haven't really made a mistake, because I can save and close the form and then immediately reopen it in run mode and get the right result to appear.
Has anyone else encountered this situation? I spend some time doubting what I've written or verifying my context, and it's starting to get very annoying, since I haven't encountered this in previos editions.
Thanks.
Found the problem to be related to the Autocorrect setting, and the manner in which Access assigns the "name" to a field you place on a form or report. With autocorrect turned "on", a change to the "name" value autocorrects to the formula, which leads to the #Name error. I haven't found a good workaround, as there are instances when you want autocorrect on and others where you want it off.
Last edited:
