Running VBA code on another computer

[focus]

I hope someone out there can help!! I have an Access database for which I
have created a number of forms and done all of the programming for them.
These forms enable the user to search, edit and enter data in the database.
All of this work was done on a computer running Windows XP and Access 2002.
The default file format is set to save in Access 2000. The application runs
fine on the computers in my office, on my home computer and on another
offsite computer. However, when the application was delivered to the client,
they have been getting errors. Initially they got "Census Table MS Access
Database Application: MSACCESS.EXE - Application Error ---The instruction at
"0x6504e339" referenced memory at "0x0000000c". The memory could not be
"read"." We had them run an MDAC update and now they get MS compiler errors
the minute they try and run a search.
The client's office is running a variety of software versions. One computer
is running WinXP w/ SP2 and another is running Win2000 - all of them are
running Access 2000. The application seems to work on some computers and not
on others - anyone have any ideas???
Thanks in advance for your help!!!

 

[John Spencer]

When I see this behavior - works on some computers and not on others I
always suspect a library reference problem.

To do its job, Access (like most modern programs) makes use of various
external program and object libraries that provide functionality that may be
shared among applications. For example, Access always uses the Visual Basic
for Applications library, the version-appropriate Access Object Library, and
the OLE Automation library. References to the specific library files,
including their locations, are stored with your database. But these library
modules may not be in the same location on different machines, especially if
they have different versions of Microsoft Office. If you move a database
from one machine to another, these references may be "broken"; that is, one
or more of the library files may not be where the stored reference says it
is.

When this happens, you need to take steps to let Access repair the broken
reference(s) ON THE COMPUTER WHERE THE FAILURE IS OCCURING.

Here are MVP Doug Steele's instructions for how to do it:

*** Quote ***

Any time functions that previously worked suddenly don't, the first thing to
suspect is a references problem.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

Just so you know: the problem will occur even if the library that contains
the specific function that's failing doesn't have a problem.

**** End Quote ****

So, follow those instructions and see if your problem goes away.

Check out the following reference
http://www.trigeminal.com/usenet/usenet026.asp?1036