<div>
You need to have specific error trapping wherein you are trapping 'expected' and unexpected errors and displaying appropriate 'friendly' error messages. &nbsp;Otherwise, you will experience the issue that is occurring in your MDE version ... just shuts down.<br />
<br />
So ... you need to add error trapping ...<br />
<br />
mx
</div>


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

<div>
Hey thanks, a response within 5 minutes. &nbsp;I'll check out your links, but sounds like exactly what I need.
</div>


Hey thanks, a response within 5 minutes.  I'll check out your links, but sounds like exactly what I need.

<div>
You are welcome ...<br />
<br />
mx
</div>


<div>
<div class="content wysiwyg-content">
I've compiled my Front.mdb database so the users run Front.mde. &nbsp;One report uses a filepath in a field to print a .jpg picture. &nbsp;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. &nbsp;My question is, why doesn't the same runtime error appear for the end user running the .mde version. &nbsp;The live system just fails, no error, no report. <br />
<a href="https://filedb.experts-exchange.com/incoming/2011/02_w09/412060/RuntimeError.doc" target="_blank" class="file-inline" title="Message displayed running  .mdb database (37 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>RuntimeError.doc</a>
</div>
</div>


RuntimeError.doc

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. 

RunTime Error Displayed in mdb but not mde database

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.