Any other suggestions.
Just one, I suppose. As you are learning VBA, you'll likely hit several snags along the way. To
help you get through such times of frustration, just keep repeating to yourself: "Macros are for
weenies; Code is Cool!" (F. Scott Barker, Access 2000 Power Programming, SAMS Publishing).
Consider the following quote from "Inside Relational Databases, 2nd Edition, by Mark Whitehorn
and Bill Marklyn, published by Springer, p 151):
"Macros offer the next level down, extending the functionality of the GUI. Macros are still
limited, however, and do not provide anything like the enormous flexibility of a programming
language. Both the macro and the programming languages take some effort to learn and,
surprisingly, often require relatively different skills; in other words, a good working knowledge
of macros may not make it much easier to convert to using the programming language. Perhaps even
more surprisingly, I do not believe that programming is fundamentally more difficult to learn.
Macros are easier to use but not by orders of magnitude."
and
"If you are new to RDBMSs, I suggest (with as much deference as possible) that you may well not
be in a position to judge whether you need macros or programming. In that case, my advice is
clear. Unless you are sure that your needs really are simple, don't bother learning to use
macros. Once you find that you need more than the GUI offers, go straight to the programming
language. In this way you avoid the pain of climbing one learning curve only to discover that the
view from the top is unsatisfactory and another climb awaits you."
</ End Quote>
Eventually, with enough practice, you should start having more and more successes with VBA.
There's lots of helpful people in this newsgroup who can assist you with problems that you
experience with your code.
Tom
____________________________
Thanks Tom.
Any other suggestions.
____________________________
It's time to wean yourself away from macros and start learning how to write VBA code. One of the
downfalls of macros is that you cannot trap for errors and respond to them gracefully. Instead,
you (or your users) will likely be presented with a really ugly macro error dialog. This would be
fairly easy to do in VBA code, although I would include a way of aborting if the process could
not be completed successfully. You might count the number of attempts, and abort if it failed 5
times, so that you don't end up in an endless loop.
There are many good books available for learning this VBA. Here is a link to a free on-line
resource for Access 97:
http://www.microsoft.com/accessdev/articles/bapp97/toc.htm
The concepts shown in these chapters should work equally well with Access 2000 or higher. I
recommend reading up on disambiguation to prevent problems related to reference priority, which
really started becoming an issue with Access 2000:
http://www.access.qbuilt.com/html/gem_tips1.html
Tom
____________________________
How do automatically get the macro to repeat if it gets an ODBC error. I am
not familiar with writing code so my only approach is via a Macro
