Fred
Thanks for the link, the 'rules' are nicely put! I wish I had known NOT to use Lookup Fields in my tables. Fortunately I found out the problem early and was able to go back and clean them all up. Never again, eh
Thanks for the advice too. For naming conventions, I picked up somewhere (sorry to author) doing something like this
tblInstalle
frmInstalle
qryActiveInstaller
rptActiveInstaller
This identifies the type of object and keeps the spaces out of the name. Do you think that this suits the long-term, or am I missing something
On error handling, I haven't 'written' any code yet. I've only pasted (or re-typed) a few short (and relatively easy to understand) codes. But I think I understand the why of using error handling and what it does. Basically, you write code that instructs (translated to English) "If the following instructions don't work, then jump to the end of the instructions and don't bother trying to finish doing the instructions.
After reading the 'Commandments' list, methinks I must learn exact syntax and go back into the app and add a few lines of code to every sub I have pasted in there
Have you got any more 'common newbie mistakes' I might try looking for or avoiding
Rick..
----- Fred Boer wrote: ----
Dear Rick
Good luck with your application development! Working with Access can be
whole lot of fun! However, I hope you don't mind a small piece of advice
from someone who started from scratch in Access a couple of years ago: tr
not to be too "impatient" as you go about learning. If I had only taken th
time to nail down the basics when I started trying to create an applicatio
in Access (way back when!), I would have had to spend *so* much less tim
fixing things up later on! I am *still* fixing problems which stem from m
improperly designed tables and relationships two years later... Also,
made many mistakes in not using a consistent naming convention in m
application, and not understanding and implementing error handling... and.
well, the list goes on! Of course, I'm not suggesting that *you* have mad
these mistakes, but making sure you get it right at the beginning will allo
you to fly much faster in the long term..
You might want to use the following as a checklist
http://www.mvps.org/access/tencommandments.ht
HT
Fred Boe
Rick Willingham said:
cover the same things. Others don't have the in-depth coverage that I'
looking for. And others are too advanced. I guess I'm too impatient t
wade through beginning VBA and learn about building dice games and no
educated enough to understand a tome like Developer's Handbookon one of the websites from the list Jeff Conrad provided. And I hav
gotten 'smart' and used the search feature (doh!) - much better now! S
this forum is proving very beneficial to me. Again, thanks to everyone fo
their support
Rick..
----- MacDermott wrote: ----
You might want to search the newsgroup archives for recommendation
on mor
advanced Access texts
If you really want a mentor, look for an Access/VB users' group i
you
area
Or if you're willing to pay, try your local IT staffing agencies They ma
have someone who'd be willing to hire out for an hour or two here o ther
for the kind of services you're looking for
if you ask specific questions in newsgroups, you'll usually ge some