My local community college is synonomous with the local discout book seller (Boarders?). I - personally - like the Que and Sybex series for MOST of the IT topics.
The Help systems are really quite good, but suffer the same 'fault' as the average distionary (" ... If I knew how to spell it I WOULDN'T need to look it up ... "

- so you need to know what to look for before looking for it. But works well for syntax and SOME of the examples are actually useful. To use the help / examples, you need to carefully understand the legaleese 'mind set' of the process, so where is says
string it REALLY means literal QUOTED string, while
string or string variable means the other ... and so on. I - personally - think MS Access is easier to learn, as VB requires you to not only learn VB / VBA, but even to get started with db manipulation you also need to get in to connectivity issues and decisions on wheather to use bound or unbound controls AND the BIGGIE - how in the real world you will generate reports (or most any printed output). Other than these issues, you can learn VB/A in either and almost universally apply that knowlege to the other.
I have the perception that many supposedly "professional" IT types think of MS Access as the lowest level of programming possible, with VB being a LARGE step up the chain. However I have used both (commercially) and really see almost NO difference in terms of VB/VBA. The trend - from my perspective - is that they are strongly convergent. If they ever actually become 'one', I really hpe the MS Access report generator AND the VB access to the printer object(s) are both retained.
MichaelRed
mred@att.net
There is never time to do it right but there is always time to do it over