Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Access 2003 issue after installing Office 2013

307 views
Skip to first unread message

charlieZee

unread,
May 5, 2014, 4:42:39 PM5/5/14
to
I have installed Office 2013 but have not run Access 2013.
After installing Office 2013, issues arise in all my Access 2003 databases when opening forms.

In one database the error displayed is:

Private Sub Command20_Click()
DoCmd.OpenForm "Cheques"
DoCmd.Maximize
End Sub

where DoCmd.OpenForm "Cheques" is highlighted in yellow.

In another database the error displayed is:

"The expression OnClick you entered as the event property setting produced the following error: Object or class does not support the set of events.

*The expression may not result in the name of a macro, the name of a user defined function, or [Event Procedure].

**There may have been an error evaluating the function, event, or macro.

charlieZee

unread,
May 5, 2014, 5:31:54 PM5/5/14
to
On Monday, May 5, 2014 4:42:39 PM UTC-4, charlieZee wrote:
> I have installed Office 2013 but have not run Access 2013.
>
> After installing Office 2013, issues arise in all my Access 2003 databases when opening forms.
>
>
>
> In one database the error displayed is:
>
>
> Looking at what I have installed on my system (as of recent) is Office 365 ProPlus.

DFS

unread,
May 5, 2014, 9:01:57 PM5/5/14
to
Open or create a module, click Tools | References (if it's still called
that in Access 2013), and it should show you any missing references to
libraries.




Larry Linson

unread,
May 19, 2014, 10:23:12 PM5/19/14
to
On Mon, 5 May 2014 13:42:39 -0700 (PDT), charlieZee
<st...@firstport.com> wrote:

>I have installed Office 2013 but have not run
> Access 2013. After installing Office 2013,
> issues arise in all my Access 2003 databases
> when opening forms.

>"The expression OnClick you entered as the event
> property setting produced the following
> error: Object or class does not support the set of events.
>
>*The expression may not result in the name
> of a macro, the name of a user defined function,
> or [Event Procedure].
>
>**There may have been an error evaluating
> the function, event, or macro.

I had a similar problem when someone installed software for me on a
new computer -- don't know what order, but A2003 and A2010 are
installed in the same folder. In the Access world, the best practice
has long been (1) install the Access (or Office) copies in the order
they were created and (2) install each one in a separate folder
(directory before we called them folders).

My old Access database worked fine after I opened it in Access 2010.
Try opening yours in Access 2013, if you haven't already.

Larry Linson
Microsoft Access MVP 2003 - 2014
Co-author, Microsoft Access Small Business Solutions, Wiley, 2010
0 new messages