D
David Burkhart
I have an Access 10 (2002/2003?) database that I wrote and split some years
ago. It runs fine on an older PC, but I need to add a new text box to one
form. The PC that I am using to make the change is newer and includes an
evaluation version of Office 2007 (Office/Access 12?). I installed Access 10
and can open the form and code in design mode, make the change, save the
change, etc just fine.
Opening the application on the new PC to test the code produces the error
message "The expression OnOpen you entered as the event property setting
produced the following error. Object or class does not support the set of
events." I did not make any changes to the OnOpen code.
When I look at the References I see that Microsoft Access 12 Object Library
is checked in addition to the Access 10 Object Library. Since the older PC
does not have Office 12 I tried to uncheck that reference, but it won't let
me. I have concluded that the presence of the Access 12 Object Library is
causing the issue.
1. Am I on the right trail?
2. Is there a fix that does not involve buying Access 12 for the old PC or
removing Access 12 from the new PC?
3. Where can I find more information on Access 10 vs. 12 issues?
Any help would be appreciated.
drb
ago. It runs fine on an older PC, but I need to add a new text box to one
form. The PC that I am using to make the change is newer and includes an
evaluation version of Office 2007 (Office/Access 12?). I installed Access 10
and can open the form and code in design mode, make the change, save the
change, etc just fine.
Opening the application on the new PC to test the code produces the error
message "The expression OnOpen you entered as the event property setting
produced the following error. Object or class does not support the set of
events." I did not make any changes to the OnOpen code.
When I look at the References I see that Microsoft Access 12 Object Library
is checked in addition to the Access 10 Object Library. Since the older PC
does not have Office 12 I tried to uncheck that reference, but it won't let
me. I have concluded that the presence of the Access 12 Object Library is
causing the issue.
1. Am I on the right trail?
2. Is there a fix that does not involve buying Access 12 for the old PC or
removing Access 12 from the new PC?
3. Where can I find more information on Access 10 vs. 12 issues?
Any help would be appreciated.
drb