Could someone please explain when you would use a macro and when you would
use VBA? So far, I've accomplished everything I need to using VBA and can't
see why you would use macro's at all.
Thanks,
Dave
Baz - 30 Jan 2007 08:51 GMT
You would use macros if you find VBA too intimidating. No other reason
whatsoever.
> Could someone please explain when you would use a macro and when you would
> use VBA? So far, I've accomplished everything I need to using VBA and can't
[quoted text clipped - 3 lines]
>
> Dave
Douglas J. Steele - 30 Jan 2007 12:42 GMT
Not quite. There's no easy way to do the equivalent of the AutoKeys macro
using VBA.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> You would use macros if you find VBA too intimidating. No other reason
> whatsoever.
[quoted text clipped - 8 lines]
>>
>> Dave
Baz - 30 Jan 2007 13:08 GMT
All of my applications have a generic form events class which every form
instantiates in it's Open event procedure. That class sinks events that I
want to be handled the same way in every form, which could easily include
KeyDown.
> Not quite. There's no easy way to do the equivalent of the AutoKeys macro
> using VBA.
[quoted text clipped - 11 lines]
> >>
> >> Dave
George Nicholson - 31 Jan 2007 17:50 GMT
The only macro in any of my apps is AutoExec, which simply calls a VBA
procedure which opens the startup form while doing other housekeeping
chores, etc.
Even that little bit could be easily worked around as long as you were 100%
sure you would never, ever, ever forget to set your Startup form (six, meet
half-dozen). A matter of personal preference (no code behind my startup
form)
Biggest drawback to macros: no error handling.
2nd biggest: VBA more robust
HTH,
> Could someone please explain when you would use a macro and when you would
> use VBA? So far, I've accomplished everything I need to using VBA and
[quoted text clipped - 4 lines]
>
> Dave