Code:
So to answer your question - you need to develop a convention that suits you. We can't tell you what that is. For me, I allow no spaces, underscores or other non alphanumeric characters, have a prefix to indicate the type (cbo=combo, btn=button, pub for public etc). I have a consistency in naming to describe the object/variable and what it does. I also keep it short so I have certain standard abbreviations I use - e.g. cust rather than customer and I use uppercase to separate the names e.g. btnCustsList, lstCusts. It doesn't always work, there are exceptions, but it works for me.
Of course, one must develop their own style no argument. I have programmed in many other languages, but nothing ever like this. It seems to have a twist, turn or wrinkle every time you turn around.
Please do not think that I am being critical, it is just every time (or most of the time) I get stuck on a error - something new pops out.
Again, please do not think I am being critical. It helps in any language if you keep working on it all the time. I do not. Also, when I see an error that I should know, it is usually because I have not worked in that area of MS Access for a for several months.
Learning MS Access 2010 is not like learning to ride a bicycle - once you learn it you never forget it. I find if I do not use it often, then I will lose it.
The best analogy I can think of is playing sports game when we were kids, when one of the players starts making new rules up on the spot. Yes, we tolerated this.
Somehow a simple game becomes complicated, it seems every time you turn around he is adding a new rule. That c or Pascal or even Fortran programming was never like this.
When I program in those languages my number one concern is making sure that I translate the algorithm correctly into code. If I fall down on the syntax, then I can also
figure it out.
In programming in MS Access my whole concern is syntax. The overall algorithm is secondary. Did I get the coding correct is my overall concern nothing else.
Again,, please do not think I am being critical - I am not.
It just seems that everything in MS Access VBA is so different.
I volunteered for this project, based on the fact that I did some VBA programming in Excel a few years back. It took one afternoon to learn that - just one afternoon.
This is very situational and particular.
It is a lot different that what I am use to.
Well, there you have it.
Hope I did not step on any toes as it was not my intention.
Respectfully,
Lou Reed