RunTime Error Displayed in mdb but not mde database

I've compiled my Front.mdb database so the users run Front.mde.  One report uses a filepath in a field to print a .jpg picture.  If the user has keyed in an invalid path (usually a typo, like an extra space), the error message isn't displayed in the .mde database, but if I copy the data and run it against my .mdb database a nice runtime error is displayed including the invalid path.  My question is, why doesn't the same runtime error appear for the end user running the .mde version.  The live system just fails, no error, no report.
RuntimeError.doc
KarenPRuskinAsked:
Who is Participating?
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Connect With a Mentor Database ArchitectCommented:
In case you need them, here are some good links on the subject:


Runtime Error Handling
http://msdn.microsoft.com/en-us/library/bb256425.aspx 

Good white paper on error handling
http://www.fmsinc.com/tpapers/vbacode/Debug.asp   

more on error handling
http://allenbrowne.com/ser-23a.html 

Global error handler
http://www.everythingaccess.com/vbwatchdog.htm      

mx
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
You need to have specific error trapping wherein you are trapping 'expected' and unexpected errors and displaying appropriate 'friendly' error messages.  Otherwise, you will experience the issue that is occurring in your MDE version ... just shuts down.

So ... you need to add error trapping ...

mx
0
 
KarenPRuskinAuthor Commented:
Hey thanks, a response within 5 minutes.  I'll check out your links, but sounds like exactly what I need.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
You are welcome ...

mx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.