Access 2003 On Open Event Error when 2007 installed

  • Thread starter Thread starter Vittles
  • Start date Start date
V

Vittles

I create and replicate about 60 different databases/year using Access 2003
(they are used for short term yet complex projects). We rely on having both
the data and any design changes synchronized (so the users can keep working
while I change the master copy to include more data elements, reports, etc.)
and this has been fully successful until now. Recently we had Office 2007
installed, keeping Access 2003 - because of our heavy replication use
(including cascading updates, etc.) and need to keep the coding available to
both types of office users.

For about 50 out of 70 users, this combination has worked perfectly - no
issues. The other 20 users (all replicated databases) experience an
"Expression On Open....: Object of class does not support the set of events"
error message upon opening the database and loading the switchboard menu form
(which is set to occur as a start up option-they never see the database
'guts' just the interface).

These users all have newer CPUs or are newer users (the only common
denominator I can figure out) and we all use these over a secure network.

Normally I would think it is a missing reference or corruption, but it seems
to be more user or computer based since I and others can open and fully
utilize the same DBs that have this issue (opening them with 2003) when
opened by any of the 20 users impacted. Those 20 users have to open them
with 2007 to have them work at all.

Any ideas as to how I can eliminate this error from occuring or what it is?
 
Good question, but no - we all have Windows XP Professional Version 2002 SP2.
We have scripted updates, and so I was thinking of a possible security
policy issue, but haven't been able to figure anything out...
 
The error we need to avoid comes up when we open these using Access 2003
(2007 works), but only for about 20 out of 70 users. I have found a few
leads that related to order of install for the MSOffice package as well as
possible administrative privileges related to having both versions on a
computer that has Vista, which I would like to test yet. We don't use Vista,
but the error messages are similar. Will post my results when I can - in the
meantime I am open to any other ideas.

Thanks! :)
 
I was able to test out a 'fix' today (found at:
http://allenbrowne.com/bug-17.html) on a new yet not used computer and you
are correct. For some reason the configuration or installation process is
not allowing the reference files or configuration process to fully complete -
thus the errors. I changed the computer registry (option 1 of the site
listed above) and the configuration runs completely whether the user uses
2003 or 2007 - both work. This registry permissions change has to be kept in
place (in case the user accidentally opens the database with 2007 again).

The odd thing about our situation is every computer was installed using the
same script, so I am not sure what happened with these 20 machines...but as
long as there is a fix, I am happy. :)

As a side note: In case anyone is in a similar situation - there is a
Microsoft KB article (http://support.microsoft.com/default.aspx/kb/928091)
that lists which order to install the office suites. I am not sure if
uninstalling and then reinstalling would have helped in this situation, but
it may have been part of the issue...

Thanks!
 
Hey,

A followup question, since I've had exactly the same issue with a much
smaller number of users (just posted a question). Does this registry change
have to be made on every user's machine? If so, I'll have to have our IT guy
do it since I'm not a system adminstrator and can't login to machines as an
administrator (not to mention the hassle for every user to have to log off,
have someone make the change, then log back in).
 
Back
Top