Visual Basic class any help for learning VBA

[Ann Scharpf via AccessMonster.com]

Re: Visual Basic class any help for learning VBA

I learn a lot by the endeavor & fail method also. But you have to at least
have some idea of what you're looking at. I'm finding this tutorial is
giving me a sense of how to maneuver around. This is just a starting point,
not an ending point to my learning.

The lessons are built off the Access objects that you get if you buy the $22
"full package" so I am having to wing it a bit. The tutorial is still
helpful for someone who knows absolutely nothing.

Lyle Fairfield wrote:[color=blue]
>Not really. But I'll indulge myself with some gratuitous comments and
>mild opinions.
>
>At one time we all knew nothing about VBA. Many of us still don't;
>we're just faking it.
>
>A major problem with much of the VBA one sees is that the persons who
>wrote it are deficient in logic and mathematics, especially the
>mathematics of sets and groups. One cannot code a poor idea or a poor
>solution well, no matter what coding skills one has. Almost everyone
>seems to start their db design with the parent entities and proceed to
>child entities; this is inefficient, ineffective and just plain wrong.
>When I see the term, "One to Many" I start to hyperventilate.
>
>Access/VBA and JET are undergoing major changes at this time. I feel
>(after only a cursory look, admittedly) that the ideas of VBA, Database
>Design and UI of the site you specified are ancient, obsolete, archaic
>and lousy. One could learn everything in all the lessons and be ten
>years behind current technology. Some of this archaic stuff is commonly
>posted as solutions here in CDMA.
>
>I learned to code by the try-and-fail method, mostly fail. I'm
>partial to that method because of it. If you had the self-discipline to
>do the same, then this newsgroup could be a great resource for you,
>especially if you took the time to try to learn who's hot and who's
>not. MVP is not a good indicator of this. Some MVPs are hot, many are
>just dull, a few spew out the party line even after the party line has
>been discredited, and at least one is bizarrely incompetent and
>verbose.
>
>Time to go do something useful.[/color]

--
Message posted via http://www.accessmonster.com

[Ann Scharpf via AccessMonster.com]

Re: Visual Basic class any help for learning VBA

Thank you.

Bob Alston wrote:[color=blue][color=green][color=darkred]
>>> Looks like an interesting site but I don't see anything about VBA on
>>> it. Am[/color][/color]
>[quoted text clipped - 19 lines][color=green]
>>
>> Bob[/color]
>YOu might look at this one. the first few courses are free. YOu could
>then see if the $99 Cd is worthwhile and also perhaps get started on
>your education.
>
>http://www.computer-training-software.com/accessvb.htm
>
>Consider these:
>
>http://www.fontstuff.com/vba/index.htm
>
>http://www.fontstuff.com/access/index.htm
>
>Some of the Access 2002 VBA modules are available free
>http://www.vtc.com/products/vbaccess2002.htm
>
>Just some stuff I found on the web.
>
>Bob[/color]

--
Message posted via AccessMonster.c om

http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/200603/1

[Terry Kreft]

Re: Visual Basic class any help for learning VBA


I would agree with much of what Lyle says here.

It is important to get a good grounding in _how_ to program and at least
some idea of what is going on behind the scenes before you start to worry
too much about learning a specific language.

Once you know enough to question, then probably the best resource you will
find on the net is this newsgroup, although it isn't a good place for
tutorials. Occasionally though someone will post a lengthy discourse on a
particular topic which are frequently good reading.


--

Terry Kreft

PS Lyle, WRT para2; will you please get that camera out of my office ! <g>.

"Lyle Fairfield" <lylefairfield@ aim.com> wrote in message
news:1142366121 .888245.38700@v 46g2000cwv.goog legroups.com...[color=blue]
> Not really. But I'll indulge myself with some gratuitous comments and
> mild opinions.
>
> At one time we all knew nothing about VBA. Many of us still don't;
> we're just faking it.
>
> A major problem with much of the VBA one sees is that the persons who
> wrote it are deficient in logic and mathematics, especially the
> mathematics of sets and groups. One cannot code a poor idea or a poor
> solution well, no matter what coding skills one has. Almost everyone
> seems to start their db design with the parent entities and proceed to
> child entities; this is inefficient, ineffective and just plain wrong.
> When I see the term, "One to Many" I start to hyperventilate.
>
> Access/VBA and JET are undergoing major changes at this time. I feel
> (after only a cursory look, admittedly) that the ideas of VBA, Database
> Design and UI of the site you specified are ancient, obsolete, archaic
> and lousy. One could learn everything in all the lessons and be ten
> years behind current technology. Some of this archaic stuff is commonly
> posted as solutions here in CDMA.
>
> I learned to code by the try-and-fail method, mostly fail. I'm
> partial to that method because of it. If you had the self-discipline to
> do the same, then this newsgroup could be a great resource for you,
> especially if you took the time to try to learn who's hot and who's
> not. MVP is not a good indicator of this. Some MVPs are hot, many are
> just dull, a few spew out the party line even after the party line has
> been discredited, and at least one is bizarrely incompetent and
> verbose.
>
> Time to go do something useful.
>[/color]

[Lyle Fairfield]

Re: Visual Basic class any help for learning VBA

Terry Kreft wrote:
[color=blue]
> It is important to get a good grounding in _how_ to program and at least
> some idea of what is going on behind the scenes before you start to worry
> too much about learning a specific language.[/color]

Yesterday I wrote an ASP/JavaScript/ADO "applicatio n". It does what I
want: I type in an SQL SELECT script or a SPROC or VIEW name; it
executes the statement and displays the returned Recordset formatted
according to a bunch of rules. Am I done? No!

Today I will get out an ancient (1982) book, Writing Efficient
Programs, by Jon Louis Bentley and assess my code against his seven
page Summary of the Rules in Appendix C. Among other things I will find
expressions which have been evaluated twice and change the script to
evaluate them once and assign their value to a variable. I will modify
my Switch (Select Case) statements so that the most likely to be true
and/or fastest least expensive tests are made first, and the least
likely to be true and slowest most expensive tests are made last.

Will this make any difference to what is seen by the user? Probably, it
will not.
Will it make any noticeable difference to the time the "applicatio n"
requires? That is very unlikely.

Then why will I take this time?
Well, the script will be easier to understand and maintain. But the
most important reason is pride. I think any work requires pride on the
part of the worker to be done well. After I have done my
assessment/revision, I will be just as happy, self-satisfied and proud
as if I had painted a picture or composed a melody.

The examples in the book to which I referred are all Pascal; this has
nothing to do with the usefulness of the book; its ideas are still good
and true twenty-four years after its printing. Good programming is good
programming, no matter what the language/technology.