By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,224 Members | 1,143 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,224 IT Pros & Developers. It's quick & easy.

Diffrence between Macro & VB code

100+
P: 222
Hello everybody

I am using access 2007.

When I use button wizard option, access 2007 use macros to implement the action.

Meanwhile Access 2003 use VB code.

What is difference between them?" in terms of efficiency & speed..."

Which method is better to use ?

Is there any option in access 2007 that I am able to change it to tell the wizard method to use VB code in place of MACROS? "actually I feel comfortable using VB code"


Does MACRO do something on access applications that VB can't do it ?


THANK YOU IN ADVANCE & BEST REGARDS


WASSIM S DACCACHE
Sep 25 '08 #1
Share this Question
Share on Google+
3 Replies


100+
P: 167
There is option to convert macros to VBA code.
Look up access help for "convert macro"
Sep 25 '08 #2

P: 50
VBA code is much more powerful than macros. Macros are there basically for beginners who don't know how to code. You can do some simple steps (run a query or a report) and not too much else.

If you know VBA code, then stick with that and avoid macros altogether.

I'm a dba at work and I see a lot of homegrown applications (built by people who have some skills in Access but who are not db professionals). Almost 100% of the time I see almost no VBA code and extensive use of macros. When I see professionally created application the opposite is usually true.
Sep 25 '08 #3

P: 69
For me, a compelling reason to use VBA rather than macros is the freedom that I then have to design error trapping, control of who uses what, and many other such needs to work just as I want. In VBA it is also much easier to design for later debugging.

When I started writing Access systems, around 15 years ago, I read all the expert advice I could find at the time and decided never to write a macro. The years since have shown me the wisdom of that decision for me.

Yes, it takes a little more effort in the earlier stages, but the later rewards are worth it.
Sep 26 '08 #4

Post your reply

Sign in to post your reply or Sign up for a free account.