[AccessD] Autoexec Code?

John Bartow john at winhaven.net
Thu Jul 17 20:02:26 CDT 2003


Well now, this certainly turned out to be a wimpy flame war! After that
enticing jab at the beginning I thought I'd see blood!

Not like Johnny Cash at all - more like that awful 70's song where some
unknown female singer who had a really high screechy voice screeched out a
love song and just about broke glass doing it. It went something like this:

loving you,
is easy cause you're beautiful,
eieieieieieieieiei!

(I can't even fit accessd lyrics into that bit)

egad, JC's too busy with spam filtering, William's nowhere to be seen and
Drew must be patching a dehumidifier into his network or something!
:o)

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John Bartow
> Sent: Thursday, July 17, 2003 11:38 AM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] Autoexec Code?
>
>
> Oh-oh,
>
> (to the tune of Johnny Cash)
>
> I hear the flame a coming...
> Its coming down the web,
> I think I know who's typing,
> just don't know when...
>
> I'm watching Access flames wars,
> heating up again...
>
> :o)
>
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Heenan,
> > Lambert
> > Sent: Thursday, July 17, 2003 9:51 AM
> > To: 'Access Developers discussion and problem solving'
> > Subject: RE: [AccessD] Autoexec Code?
> >
> >
> > What is your problem (and all the others out there who have
> hang-ups about
> > the "dreaded" macros)? <g>
> >
> > I use macros for two reasons only myself (to run stuff in
> AutoExec and to
> > disable/enable certain keystrokes in the AutoKeys macro), but I don't go
> > around chastising myself for doing so. They do what I need and
> as there is
> > no need for error handling I don't miss that ability. I *don't*
> use macros
> > for anything else because I can do what I need in VBA with more control.
> >
> > You then say "I have one form that opens via the startup dialog
> > and put the
> > code in there that opens my hidden form.  It works, but doesn't
> seem like
> > the best way to do it". What makes you think it's not "the best way"?
> > Because you have the overhead of opening a form in order to open another
> > form? If that's such a big issue (is it???) then put ONE
> "RunCode" line in
> > AutoExec to call a function in a module - that's the *ONLY* way
> > that you can
> > "autoexecute a MODULE".
> >
> > Please, don't stay religious about macros. You might just as
> well say that
> > using  #define in C/C++ is bad because it's not real C/C++
> code, but they
> > are part of the C/C++ development environment, and everyone uses them.
> > Occasionally you need to use macros in Access, but it's no sin to do so.
> > <vbg>
> >
> > Lambert
> >
> > > -----Original Message-----
> > > From:	Greg S [SMTP:weeden1949 at hotmail.com]
> > > Sent:	Thursday, July 17, 2003 10:26 AM
> > > To:	Access Developers discussion and problem solving
> > > Subject:	[AccessD] Autoexec Code?
> > >
> > > Hello Group!
> > >
> > > I know that part of my question has been discussed before but I
> > can't seem
> > > to find it (too shor a night I think...).
> > >
> > > 1.  I want to open a hidden form on startup that opens to a
> table in the
> > > BE.  The purpose is to keep the BE open until the last user
> exits.  This
> > > "should" speed up some of the timing issues I've been having
> at a local
> > > client (large network, some fiber connections, but some older
> > switches and
> > > servers).  It's a fully secured app, so I can't directly open
> > the table by
> > > the form...it has to be done thru a query since none of the users have
> > > permissions on the tables.
> > >
> > > 2.  Related to that, I could just put the code in the AUTOEXEC
> > macro that
> > > opens the form hidden.  But I HATE macros.  They're
> functional, but that
> > > doesn't make me like'em any better.  I have one form that
> opens via the
> > > startup dialog and put the code in there that opens my hidden
> form.  It
> > > works, but doesn't seem like the best way to do it.
> > >
> > > 3.  Is there some way to autoexecute a MODULE or some of the
> code (other
> > > than the way I'm forcing it with the form above in #2)?
> > >
> > > Btw, it's Access 97, soon to be changed over to Access 2002,
> or .net, or
> > > xp or whatever they want to call it this week...
> > >
> > > Thanks!
> > > Greg Smith
> > > Weeden1949 at hotmail.com <mailto:Weeden1949 at hotmail.com> << File:
> > > ATT10294127.txt >>
> > _______________________________________________
> > 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
>
>




More information about the AccessD mailing list