Issue with Access 2003

[Rob Bunocore]

I have a situation where I have build a database in Access 2002. I
save it as a MDE file and distribute it to three users at different
locations. All three users have Access 2003. I'm not sure who
installed Access on their computers.

The database works fine on my computer and two of the other computers,
but one users receives errors.

"The expression On Click you entered as the event property setting
produced the following error. The Open Form action was canceled.

The expression may not result in the name of a macro.....
There may have been an error evaluating the function....."

I understand the error, what I don't understand is why it would work
fine on three computers and only error on one. Of course I can not
duplicate the problem on my side. Plus, if she clicks OK and then
tries it again, it works without error.

Am I missing something?

Any help is appreciated. Thanks.

Robby

 

[Tony Toews [MVP]]

The database works fine on my computer and two of the other computers,
but one users receives errors.

"The expression On Click you entered as the event property setting
produced the following error. The Open Form action was canceled.

The expression may not result in the name of a macro.....
There may have been an error evaluating the function....."

I understand the error, what I don't understand is why it would work
fine on three computers and only error on one. Of course I can not
duplicate the problem on my side. Plus, if she clicks OK and then
tries it again, it works without error.

References problem.

Do you have any references besides the basic three? Are you sure you
need them? Write down the path and name of the extra ones, delete
from the references list and Compile and Save All. Keep any
necessary references and ensure they are distributed to the target
system.

For a very detailed page on reference problems see
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

Ctrl+G will take you into the Debug/Immediate window. Then click on
Tools on the menu bar and References.

The Access 2003 default references when the MDB is in A2000 format are
Visual Basic for Applications
Microsoft Access 11.0 Object Library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.1 Library

The Access 2003 default references when the MDB is in A2002/A2003
format are
Visual Basic for Applications
Microsoft Access 11.0 Object Library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.5 Library
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Rob Bunocore]

I do have a number of references:

Visual Basic for Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 library
Microsoft Windows Common Controls 6.0(SP6)
Microsoft DAO 3.6 Object Library
Microsoft Office Web Components Wizards
Microsoft ADO Ext. 2.8 for DDL and Security

I removed
Microsoft ActiveX Data Objects 2.1 library
Microsoft Windows Common Controls 6.0(SP6)
Microsoft Office Web Components Wizards

I saved and it still complied without error. I do get nervous
removing referrences. Do you think this affect the program at all.
Plus, does it matter that I have MS Access 10.0 Object Library instead
of Access 11.0 Object Library.

Robby

 

[Tony Toews [MVP]]

I do have a number of references:

Visual Basic for Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 library
Microsoft Windows Common Controls 6.0(SP6)
Microsoft DAO 3.6 Object Library
Microsoft Office Web Components Wizards
Microsoft ADO Ext. 2.8 for DDL and Security

I removed
Microsoft ActiveX Data Objects 2.1 library
Microsoft Windows Common Controls 6.0(SP6)
Microsoft Office Web Components Wizards

I saved and it still complied without error.
Good.

I do get nervous
removing referrences.

Understandable but if it compiles you should be fine.

You may also need to remove Microsoft Windows Common Controls 6.0(SP6)
as that is likely to be a source of your troubles too. However that
one may be more difficult as you may actually be using a common
control item such as the calendar control.

See the Calendar Tips page at my website
http://www.granite.ab.ca/access/calendars.htm

There could, likely will, be lots of version problems when you go to
distribute the MSCal.OCX..

One alternative is MonthCalendar is a completely API generated Month
Calendar derived directly from the Common Control DLL. There are
links to several downloadable calendar forms at my website. As these
are forms you can also do anything with them you want.

You can also use the calendar form which comes in the Access <insert
your version here> Developers Handbook by Litwin/Getz/Gilbert,
publisher Sybex www.developershandbook.com. These books are well
worth spending money. Every time I open one I save the price of the
book.

If you are using other controls then see
How do you get rid of troublesome ActiveX Controls/references?
http://www.granite.ab.ca/access/referencetroubles.htm

Do you think this affect the program at all.

If you compiled without an error then it is highly unlikely that you
will have a problem.

Plus, does it matter that I have MS Access 10.0 Object Library instead
of Access 11.0 Object Library.

No, you have no control over that reference. Access automatically
changes it depending on your version of Access.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm