home *** CD-ROM | disk | FTP | other *** search
- Deciding When to use Macros and When to use Access Basic
-
- Summary:
-
- Because Access provides two forms of programming, macros and Access
- Basic, there is the potential for confusion as to when you should use
- one form of programming rather than the other. This article discusses
- some tips on how to choose between macro programming and Access Basic
- programming.
-
- More Information:
-
- Access has a very effective user interface that is powerful enough to
- accommodate most needs. However, like many other database products,
- Access provides the user with the ability to develop his or her own
- way to manipulate the power of the product.
-
- One distinct advantage of Access over other products is that the user
- has a choice of two levels of programming: macros and Access Basic.
- These two programming languages are designed to complement each other.
-
- As a rule, you should write your applications using macros and then
- supplement the application with SUB and FUNCTION procedures when you
- encounter a programming situation that a macro cannot easily
- accommodate.
-
- Wizards are an example of a program you can write that is beyond the
- capability of a macro. Wizards require functionality that cannot be
- duplicated by a series of macro actions. Having to resort to Access
- Basic should not be a common occurrence for most mainstream database
- applications, however.
-
- Knowing when to use modules instead of macros is easier when you
- understand how Access works. If you understand and are familiar with
- Access, you will find that it is easier to determine when modules are
- required to accomplish a specific task.
-
- New users of Access will likely be surprised at the ease, power, and
- versatility that Access macros can provide.
-
-