[AccessD] Framework Discussion - Who's following this

My objective with this discussion is to explain the concepts and
implementation of frameworks in sufficient detail that anyone willing to
learn can pick up at least a few new ideas, understand classes and how they
can solve problems, understand withevents and how using them allows us to
encapsulate entire subsystems into an object, and understand Frameworks and
how and why they might be useful.  I know that this is a rather large
objective, and that some of these subjects seem rather deep.  I am
attempting to keep the details clean and uncluttered in the beginning so
that you can not get bogged down in stuff not relevant to the specific
subject of the specific post.

In order to accomplish this objective I need to get a feeling for who is
following this discussion and at what level.  Would everyone interested in
this thread please answer the following questions:

1) 	Interest Level
	a) I already pretty much do what you are discussing, just wanted to see how
you do it.
	b) I am extremely interested in this concept and subject, would probably
use it if I can figure it out.
	c) I am interested and might start using some of this stuff.
	d) Moderately interested, probably too much work for what I see getting out
of it
	e) Marginally interested, probably never use any of it.

2)	Understanding
	a) I understand completely what is going on
	b) I mostly follow what is happening but have a couple of things I don't
really understand
	c) I am trying my best but can't really follow a lot of it
	d) Hopelessly lost, want to understand but need you to slow down a bit.

3) 	Participation
	a) I am scanning the posts lightly to just get the basics
	b) I am reading it and attempting to follow the examples.
	c) I am reading the posts and working through the included code, and have
downloaded the example database
	d) I am reading and have downloaded the database, and have worked through
the examples in the database to see how this stuff works.

I truly appreciate your participation.

Thanks,

John W. Colby
www.ColbyConsulting.com