Training suggestions

[dickfoto]

I am doing more programming in Access and the books out there are great. But most assume VBA knowledge and other things that someone who dabbles may not understand. Is there any training program that anyone knows that goes past the basics and teaches some nitty-gritty - tips and tricks, VBA - stuff to do in the background, not always depending on the program to do it all for you.

Suggestions would be welcome. Also, any text you think would be worthwhile is also useful information.

Thanks!

 

[The_Doc_Man]

In my 35+ years in the programming industry, I have always found that the best way to learn something is to see how someone else does it. Then, if you happen to see a better way, you can apply it. But the more important idea is EXPOSURE. Exposure to ideas, methods, good practices. In classes, the prof doesn't just give you the theory on doing something. He shows you code fragments designed to achieve some goal.

Go to any large bookstore chain. Find a couple of books on Access - or on Office. See how much space they dedicate to VBA. It doesn't matter that the code is somewhat obscure. To a beginner, all code is obscure. You need to see how things are done. You won't get it right the first time, maybe. (Which is why you always make backup copies of databases even when only in the development stage.)

Get more than one book if two are available. If you didn't originally install the samples, re-install Access to include the samples such as Northwind and the other DBs they provide as templates. Open up the code areas on the forms and reports (class modules) and the general code (general modules). See what they do. In the various controls on each form or report, look for things like event or macro triggers.

Identify the options frequently used on forms and reports. Open the property sheets in the examples. Use the F1 key to make the cursor have a question-mark in it, then click on any property that doesn't make sense to you. Access has context-sensitive help. Don't be afraid to dig around and get dirty among the dusty old code you see. (Trust me, bit dirt washes off cleanly.)

Another thing to try: Use the form wizards and control wizards to do some things, like create auto-lookup options or command buttons. Open up the forms created that way. Look at the properties and code generated for the things you built. The wizards are not the sharpest knives in the drawer BUT they get the job done. Eventually, you will learn to recognize clunky from elegant. Until then, don't shoot for elegant. Shoot for functional.

At first, you will learn things by rote using this method, but each new failure or success will give you some new insights. Visit this forum now and then. (And others.) Learn how many folks visit the same problem in different ways. (Trust me, if you see five people attacking a problem, each will have a different approach.)

Finally, don't hesitate to ask questions, though I would personally prefer that you also learn how to search this forum before you ask detailed techie questions. Sometimes you'll find your answers in the forum's archives.

 

[Newman]

When I started to learn programming, I bought a game in QBasic which was open source. I looked at the code and tried to understand the best I could. then I start changing it bit by bit and kept on looking at what was happening. I did so until the game was the way I liked it. And I learned a lot in the process.

So, as Doc suggested, I would start with a full database (Northwind or someone else's) and look at the code. Then, when you think you understand something, change it, one thing at a time, and look at the result. Have fun doing it.

Make your own database just for fun. If you are a golfer, make a database to collect your scores, hooks, club used, etc for each golf courses and even each holes. If you are a music fan, make a database to collect informations on artists, concerts, albums, etc.

You'll soon find out that it is much easier to do it if it is for pleasure. You'll have less pressure and you'll see it live, instead of just reading it in books, which tends to be boring.

Also, learn to use the breakpoint, variable window and spy window. They come handy when you want to see what a string of code does.

Have I said «Have fun»?