Re: Handling Bugs
- From: "Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx>
- Date: Sat, 13 Dec 2008 17:06:52 -0700
"Linq Adams via AccessMonster.com" <u28780@uwe> wrote in message
news:8e9f64a6219bd@xxxxxx
Are you, in fact, compiling your code prior to distribution? This should
help
pinpoint errors and allow you to correct them before the great unwashed
are
given access.
Keep in mind that while you can compile your code before you distribute it
by going debug->compile from the code menu, keep in mind that if you
distribute a mdb, then any on handled error will cause your to lose all
application to loose all variable values.
More importantly and more specific to this issue, is the posters said that
he's distributing via the runtime and errors are causing his application to
shut down. Keep in mind that any un- handled error in the runtime is a much
worse affair, since it causes the whole thing to SHUT DOWN.
This shutdown occurs right after the users clicks to dismiss the dialog
box that pops up when you got an error.
So while in the regular version of access a un handled error causes you to
blow out all your local and global variables, when it occurs in the runtime,
it not only loses all the variables, when you click OK to dismiss the dialog
box that tells you about the error, the whole access runtime actually
terminates and shuts down.
The user at this point will then have to relaunch the
application and it also possbile they lost some work.
So we're not talking about compiling errors in the code, we are talking
about code without error handling....
My whole point here is that if the user uses a mde, not only do variables
never get blown out, but in the runtime those un-handled errors does not
cause the whole system to shut down.
This 100% shutting down of MS access is normal and typical behavior when you
deploy a regular mdb file with the runtime.So, there is
two significant and important benefits to distributing your
application as an mde.
So, the issue of making sure one's code having compile errors is important,
but not compile errors, but un-handled errors in the runtime that causes
this shutdown.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
.
- Follow-Ups:
- Re: Handling Bugs
- From: Frank Wagner
- Re: Handling Bugs
- From: Frank Wagner
- Re: Handling Bugs
- References:
- Handling Bugs
- From: Frank Wagner
- Re: Handling Bugs
- From: Albert D. Kallal
- Re: Handling Bugs
- From: Linq Adams via AccessMonster.com
- Handling Bugs
- Prev by Date: Re: Handling Bugs
- Next by Date: Re: Frustrated - Creating Auto Number
- Previous by thread: Re: Handling Bugs
- Next by thread: Re: Handling Bugs
- Index(es):
Relevant Pages
|