Access / VBA
Home ] Access - Start Here ] Excel In Depth ] MS Office ] Visio Info ] Creating Web Pages ] Technical References ] Viruses ] Points of View ] Gadgets ] Just Links ] Monash ]

   Search this site or the web       powered by FreeFind
  Site search Web search

Participate in Ananda's Discussions
Post a message

Monitor page
for changes
   it's private  

by ChangeDetection

VBA Resources
Programming Access

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 and peers.

  1. 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".
  2. 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 some cheer.

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 dialog.
      • 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.

More Details:

VBA Resources
Programming Access