Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / May 2008

Tip: Looking for answers? Try searching our database.

Runtime error message --- only one user

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Craig - 09 May 2008 13:55 GMT
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 - 09 May 2008 16:14 GMT
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

> Hello,
>
[quoted text clipped - 31 lines]
> Thanks,
> Craig

Rate this thread:






 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.