Runtime error message --- only one user

[Craig]

Hello,

I have a split database that holds miscellaneous HR information, and is
being used by approximately 40 people at my company. Approximately 5-10
people access the database simultaneously, using the runtime version of
Access, via a local front end that is linked to the back end on a server.

Everything was working fine for about a month after deployment until this
week, when one user started getting a runtime error anytime he would try to
run a report (any report) from the database. (All other functions work fine
for him.) The error:

"Execution of this application has stopped due to a run-time error. The
application can't continue and will be shut down."

No other user gets this error, and the user in question had not been getting
this error until the last week. I am unable to duplicate this error on my
own PC.

The same error occurs no matter where in the database he tries to run the
report (there are several forms that allow users to run reports). To give
one example, a form called frmIncidents has a button called btnPrintCurrent,
and the subroutine btnPrintCurrent_Click has error-handling.

Is there any way to see what is causing this run-time error or get more
specifics?

Has anyone else experienced this kind of run-time error? Is there any
additional information I can provide that might give a clue as to what is
causing it?

Any help is greatly appreciated.

Thanks,
Craig

 

[John Spencer]

I would suspect that the user has no default printer defined. Or that they
have a printer driver that Access won't work with.

So first, try defining a default printer. If one is already defined, see if
you can define a different printer as the default printer.

John Spencer
Access MVP 2002-2005, 2007-2008
Center for Health Program Development and Management
University of Maryland Baltimore County

 

[Craig]

John,

Thanks for the advice. Unfortunately the cause of the error seems to lie
elsewhere.

The user in question DID have a default printer defined, although it was a
nonexistent inkjet printer (strange). I redefined the default printer as the
shared network printer, which several other database users are able to
successfully print to, but it still came back with the same error ("Execution
of this application has stopped...") when attempting to run/print the report.

However, not to get pointed in the wrong direction, I should point out that
the error also occurs when simply attempting to run a report (but not
physically print it). However, when only running a report, the error is
different:

"MSACCESS.exe has generated errors and will be closed by Windows. You will
need to restart the program. An error log is being created."

I'm not sure where this error log exists or how to access it --- or whether
it would provide any clues about what's causing the runtime errors.

To reiterate, these errors only occur for this single user. All other users
are able to use the database with full functionality and no problems.

Any help is greatly appreciated.

Thanks,

Craig

 

[John Spencer]

Obviously, something is different for that user.

Some things to check/try.

-- Check the printer driver and make sure it is the same version as the other
users

-- Load a fresh copy of the database on the user's computer

-- Check the Access Version and see if it is the same version (including
updates) as the other users

Beyond that I am out of ideas

John Spencer
Access MVP 2002-2005, 2007-2008
Center for Health Program Development and Management
University of Maryland Baltimore County

 

[Craig]

John,

Your last point got me thinking: I've got the application set up to use the
Microsoft Access runtime version.

I think (although I'm not sure) that the user who is having the problem is
somehow running the application under Microsoft Access Runtime 2000, whereas
everyone else is using 2003.

My questions:

1. Are there 2000 and 2003 version of Microsoft Access Runtime?

2. If so, how do I confirm that the trouble user is on 2000 and not 2003?

3. If he is on 2000, how do I force his computer to use the 2003 version?
(I had thought I included the 2003 version with the installation package, but
he has MS Office 2000 on his computer and I think that somehow it may be
drawing 2000 runtime from that?)

I apologize if these seem like silly questions but I am about at the end of
my rope trying to figure out the cause of this problem!

Thanks again for all your help,

Craig