[AccessD] Autoexec Code?

Big Sigh of Relief...

Greg,

Glad to hear that you are not really a macro basher, I'm not really a macro
evangelist either. It's just that I bristle when I see comments along the
lines of "macros must be avoided, they are bad. Period!" (not that that's
what you said either).

I *do* agree with most people who advise not to use complex ("complex" -
more than one or two lines) macros because of the difficulty of debugging
them.

As for the general question "what's the best way to...", one rule I always
try to keep in mind is that if I'm running code in a loop that repeats a lot
I want that code to be as fast and efficient as I can make it, but it it's
something that's run once or rarely then there's little point in putting a
lot of effort into shaving a few milliseconds off the execution time. The
users will never notice it.

Lambert



> -----Original Message-----
> From:	Greg S [SMTP:weeden1949 at hotmail.com]
> Sent:	Thursday, July 17, 2003 3:00 PM
> To:	Access Developers discussion and problem solving
> Subject:	Re: [AccessD] Autoexec Code?
> 
> BIG sigh.
> 
> Lambert;
> 
> It's not that I 'really' hate macros...they do work.  And sometimes it's
> the
> only way to get some things done (they can be quick to use and make up,
> which is a +...).  I guess I should've asked directly if there were a
> better
> way to do what I wanted than through a macro.  I'm not into Macro
> Bashing...<vbg>...
> 
> The 'opening a form to open another form' isn't really an issue since that
> first form ALWAYS opens anyway.  And rephrase my one comment to say "is
> there a different way to do this"...
> 
> Sorry about trampling macros...;)
> 
> And thanks for the info --- Jim and Lambert
> 
> Greg
> 
>