as nobody has answered this, i will make a few comments
assuming you have a basic concept of any procedural computer language, then access vba isnt so different
the main thing is to understand what is happening with the event driven model. you dont have to programme everything sequentially - you just have to decide what to do in response to particular events -which means you need to understand which events may potentially interfere/interact with one another within your app - but the programming of each event is pretty well no different to any other procedural language - ie VBA is bascially VB
so the other thing is "how to programme" - and thats where i think a course is difficult. i think programming is not really teachable as such. often all that is needed is a prod in the right direction from experienced practitioners. you can get 90% there without help, but to get the extra 10% "light-bulb flashing" often just needs a prod in the right direction. Which isnt the way a formal course goes.
eg - an early MS database app, showed a CD colelction with a tracklisting for each album, and a total time for the album. At the time I wanted to clarify how they got the total time - and I found they didnt - they re-entered the time, directly INSTEAD of calculating it from the track times. And I found that doing this sort of thing, although second nature once you understand it - just isnt made clear in many primers.
so in my opinion, the secret to programming is just hours and hours of practice, with some judicious pointers along the way.
--------------
to this end, the single best resource i ever found was the Access Cookbook (O' Reilly) Its not a primer - it just takes a number of practical problems, and solves them with interesting, and fairly advanced VBA techniques. Well worth a look
