[AccessD] [Spam]8.31 Re: The command you specified is not available in an .accde database

ERL is always "enabled". If there are no line numbers, ERL will return 0.
If only some lines are numbered, it will report the last line number encountered before the 
error  (0 if the error is raised before the first numbered line).

-- 
Stuart

On 19 Jun 2011 at 9:34, Mark Simms wrote:

> I take it that Erl is only enabled when line numbering is turned-on ?
> That is for both Excel and Access vba then ?
> 
> 
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com [mailto:accessd-
> > bounces at databaseadvisors.com] On Behalf Of Darrell Burns
> > Sent: Saturday, June 18, 2011 9:59 PM
> > To: 'Access Developers discussion and problem solving'
> > Subject: Re: [AccessD] [Spam]8.31 Re: The command you specified is
> > not available in an .accde database
> >
> > Thanx Bill, I finally got the answer off another forum...it's "Erl".
> >
> > Here's how I use it now in my error handlers:
> > MsgBox "Error " & Err.Number & " (" & Err.Description & ") in
> > procedure GoToDirect of VBA Document Form_Asset_Master",
> > 	vbExclamation + vbOKOnly, "ERROR" + IIf(Erl > 0, " Line # " & Erl,
> > "")
> >
> > It's already helped me pinpoint a hidden bug.
> >
> > -Darrell
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William
> > Benson Sent: Saturday, June 18, 2011 11:34 AM To: Access Developers
> > discussion and problem solving Subject: [Spam]8.31 Re: [AccessD] The
> > command you specified is not available in an .accde database
> >
> > Perhaps a property of the err object which you can examine in your
> > error handler section.
> >
> > Bill Benson
> > Owner
> > VBACreations, LLC
> > On Jun 17, 2011 8:05 PM, "Darrell Burns" <dhb at flsi.com> wrote:
> > > I actually did find the culprit, Doug. When the app starts up it
> > > runs
> > a
> > > subroutine that opens each form in design mode to determine its
> > > recordsource. This works just fine in an accdb but, of course, an
> > accde
> > > doesn't allow it.
> > > Now that I've reprogrammed that whole module, it works fine in an
> > accde,
> > but
> > > now I've got something holding me up in the runtime version. A
> > > form
> > that's
> > > normally opened from a Switchboard button won't open. This time,
> > > no
> > error
> > > message. I took your advice and installed MZTools and added line
> > numbers.
> > > Now how do I display the offending line # in my Error message?
> > >
> > > -----Original Message-----
> > > From: accessd-bounces at databaseadvisors.com
> > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug
> > Murphy
> > > Sent: Friday, June 17, 2011 10:50 AM
> > > To: 'Access Developers discussion and problem solving'
> > > Subject: Re: [AccessD] The command you specified is not available
> > > in
> > an
> > > .accde database
> > >
> > > If you use MZ tools put add line numbers to the routines that run
> > > on
> > start,
> > > and put the line number of the line that fails in your error
> > > message.
> > This
> > > will give you the routine and line that fails.
> > >
> > > -----Original Message-----
> > > From: accessd-bounces at databaseadvisors.com
> > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darrell
> > Burns
> > > Sent: Friday, June 17, 2011 9:43 AM
> > > To: 'Access Developers discussion and problem solving'
> > > Subject: [AccessD] The command you specified is not available in
> > > an
> > .accde
> > > database
> > >
> > > Hello.
> > >
> > > I have an A2007 app that starts up with a Login that opens a
> > switchboard.
> > It
> > > works fine as an a accdb, but when I saved it as an accde I get
> > > the following error message:
> > >
> > > "The expression On Open you entered as the event property setting
> > produced
> > > the following error: The command you specified is not available in
> > > an
> > .mde,
> > > .accde, or .ade database."
> > >
> > > I can't put a trace on it because it's an accde. Could it possibly
> > > be complaining about this command..."Set CurrProj =
> > > Application.CurrentProject"?
> > >
> > >
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>