KCL
asked on
control name "xxx" is misspelled or refer to a control that doesn't exist
Hi,
I am having 2 related weird problems with Access 2007.
1. Sometimes I get an error message "The control name "xxx" is misspelled or refer to a control that doesn't exist" when I use the embedded macro to build actions. However, I am 100% positive I am doing things right. Also, this error dissolves when I convert the macro to visual basic code. What happened here?
2. I am transferring the database to another computer when I finish creating my database and tested out without errors on my computer. The same error message above suddenly appears in the new computer. Why? It seems like I need to convert all those embedded macros to visual basic codes to avoid this problem but I don't understand how can the database work on one computer but suddenly not on another computer.
Thank you.
I am having 2 related weird problems with Access 2007.
1. Sometimes I get an error message "The control name "xxx" is misspelled or refer to a control that doesn't exist" when I use the embedded macro to build actions. However, I am 100% positive I am doing things right. Also, this error dissolves when I convert the macro to visual basic code. What happened here?
2. I am transferring the database to another computer when I finish creating my database and tested out without errors on my computer. The same error message above suddenly appears in the new computer. Why? It seems like I need to convert all those embedded macros to visual basic codes to avoid this problem but I don't understand how can the database work on one computer but suddenly not on another computer.
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.