Yes in one of my teams of 12, 8 were left handed.
I can also say from some experience, and the point I think may apply to Lol999, is that here are some teachers/educators that have a knack for teaching; getting the concepts across; leading/directing and getting the "student/learner" to appreciate the concepts and try/experience the learning process. And there are others who'd rather be fishing or drinking or anywhere else doing anything else.
There are many people of all different backgrounds who feel the M$oft products are all similar. For example, I've heard this so many times -Access is just a big brother of Excel---Wrong! They are different products, based on different object models and serve different audiences/situations. Similarly there are many competing DBMS product so Acces is not better than Oracle and Oracle is not better than SqlServer --- it is dependent on several factors as to which is applicable/affordable/available....
Anyway back to the intent of this thread. You start with a business issue/problem or opportunity. You get it clearly identified /documented. Get feedback to ensure the issue is clear and complete. You look at some options. Identify what is feasible? What resources/skills are needed? Create some mockups/prototypes get continuous feedback, update requirements etc. Get others involved so it becomes "our solution", not "the programmer built this"!!!
See my post on
stump the model for more info.
Bottom line is you have to understand the problem/opportunity and you have to do the analysis. You can't jump into physical Access without some form of clear requirements. Models, prototypes, communication sessions, and especially those where you plant a misconception/error and let the others/users point out the "flaw" you made.
Helps get people onside. So much for the soap box.
Oh yes, I do most things left handed, but write right handed.
Just saw Lol999's last post when I posted. I have 4 grand kids --- 2 are left handed.
