Hi. I'm sort of a newbie, so please bear with me.

I have created a wonderful (imho database, which works just fine when
powered by Access 2007. However, when I try to power with Runtime, I get
error city. Without going into detail with regard to any specific error, are
there broad classes of errors that would trip up the program in Runtime, but
not in Access? Wondering if there are some general things I can keep my eyes
open for when writing/fixing code?

Thanks for any input!
Kim M.

Hi Kim,
been there, done that.
It is quite an eye opener to find that the runtime gives so many errors.
You need error handling code on every sub and function in a runtime app.

In other words, every unhandled error in a runtime app is a show stopper.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


"Kim M." <(E-Mail Removed)> wrote in message
news:444FBF9A-4314-4DAC-AD41-(E-Mail Removed)...
> Hi. I'm sort of a newbie, so please bear with me.
>
> I have created a wonderful (imho database, which works just fine when
> powered by Access 2007. However, when I try to power with Runtime, I get
> error city. Without going into detail with regard to any specific error,
> are
> there broad classes of errors that would trip up the program in Runtime,
> but
> not in Access? Wondering if there are some general things I can keep my
> eyes
> open for when writing/fixing code?
>
> Thanks for any input!
> Kim M.

"Jeanette Cunningham" <(E-Mail Removed)> wrote in message
>
> In other words, every unhandled error in a runtime app is a show stopper.

Actually, if you distribute a mde, or accDE, then unhandled errors are
ignored, and they don't even re-set your variables!

So, a great suggestion here is to simply always use a mde or accDE for the
resulting application. This approach allows one to even use global variables
and they NEVER will be re-set..even if an error occurs.

The 2nd big bonus is that un-handled errors don't cause the application to
shut down. They do if you using a accDB, but accDE just keep on
running...they are very robust and hard to kill...



--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(E-Mail Removed)

"Jeanette Cunningham" <(E-Mail Removed)> wrote:

>been there, done that.
>It is quite an eye opener to find that the runtime gives so many errors.
>You need error handling code on every sub and function in a runtime app.

FWIW this task becomes more manageable when using MZTools "Add Error
Handler" button. Granted you have to review and click in every code
module in your database but still better than copy and paste, etc.
Besides the MZTools button places the name of the procedure and object
in the error message for easier debugging.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/

<<MZTools "Add Error Handler" button. >>

Tony, can you tell me more about this? Where can I get it/find it?

TIA,
Kim M.

"Kim M." <(E-Mail Removed)> wrote

> <<MZTools "Add Error Handler" button. >>
>
> Tony, can you tell me more about this? Where can I get it/find it?

http://www.mztools.com/index.aspx

The one you want is "MZ-Tools 3.0 for VB6 and VBA".

Larry Linson
Microsoft Office Access MVP