What this is about
Here are some resources that I am linking together for teaching/discussing Access / VBA.
Feel free to use these to study and research. If you want to instruct others
using this approach, do send me a note so I know that I'm contributing to your
efforts and well being. I suppose you could call this web page AcknowledgementWare.
Programming with VBA
I teach a 2 day Access/VBA courses and Excel/VBA courses.
Sometimes, I dabble in Word/VBA. Here are my perceptions from the participants
- Although I find my the VBA / IDE is now my natural
development environment, and I "see" and interact with it
successfully, it is curious that many others don't "see". The
symptom or message or error may be really apparent to me, but many first
timers don't. After longer experience, these first timers now become build
up "flying hours" in developing VBA applications, but they may
still not "see".
- The apparently trivial / simple features can so frustrate
and upset first time coders, that they get disheartened and "throw in
the towel". This is a sorry situation and I do my best to bring them
Hurdles to Overcome
- Reading, Seeing and Digesting the signals and feedback from
the VBA/IDE. Take time to understand:
- the workings of the VBA Editor
- define unique colours for Keyword and Identifier so
that you make the colours tell you when:
- Keyword (I prefer Blue)
- Identifier (I prefer Pink)
- Syntax Error (factory defaults to Red)
- Remarks (factory defaults to Green)
- Strings (factory defaults to Black)
- get experience when the environment clearly tells
you via the colours that you have typed in wrong syntax.
- get experience when the environment does NOT give
you signals but the Debug, Compile menu item throws out an error
- get experience when neither the environment nor the
Debug, Compile menu throws out any error signals but you will have a
runtime error when you execute your code.