[dba-Tech] Access vs. .NET

Hi John
 
I see. But how do you (or any other following this thread) manage
that?
 
/gustav

>>> jwcolby at colbyconsulting.com 18-11-2004 16:51:42 >>>

The end user in this case is the programmer.  The programmer is
presented
with well over 3000 classes, of which probably 300-500 are normally
"useful"
to the programmer.  The rest are parent, grand parent objects etc back
up
the inheritance chain.  Most of those objects are not really very
useful on
a day to day basis, but they are documented and their documentation
obscures
the vision.  Kinda like the forest for the trees.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: dba-tech-bounces at databaseadvisors.com
[mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Gustav
Brock
Sent: Thursday, November 18, 2004 10:42 AM
To: dba-tech at databaseadvisors.com
Subject: RE: [dba-Tech] Access vs. .NET


Hi John

What do mean saying "end user stuff". Do end users program in .Net?

/gustav

>>> jwcolby at colbyconsulting.com 18-11-2004 15:33:45 >>>

Yep, bewilderment is allowed.  The biggest issue in my opinion with
.net is
that while 9/10ths of the classes are not end user stuff they still
have to
expose them (and document them) since with true inheritance it is
possible
that you will need to get at them every once in awhile.  It would be
nice if
it were organized such that the end user stuff were all that you saw
unless
you "pressed a button" to show the parent objects.  

The other thing is that the organization, the presentation is totally
different from Access.  We simply aren't used to it.  Because in
Access
inheritance doesn't exist per se a lot of the things (windows of
information) that are required in .net aren't needed in Access.  It is
absolutely overwhelming when you first get started.