[dba-Tech] Access vs. .NET

John,

>> I did enter data into a vt100 with a punched card drawn on the screen were you had to enter the FORTRAN syntax into specific columns.  YUK! <<

The old VT-100, eh? Back when audible keystroke feedback was deemed desirable. I have to admit that I liked the keyboard click on the original DEC Rainbow 100 (you could mute it if you wanted to), as well as the scooped-out F, J, and 5 keys for home-row location.

As far as that card drawn on the screen, sometimes I think that we as developers aren't making it obvious enough for our users. Back then there were RULES and, by God, you FOLLOWED them!

Steve Erbach
Neenah, WI

> ------------Original Message------------
> From: "John W. Colby" <jwcolby at colbyconsulting.com>
> To: "'Discussion of Hardware and Software issues'" <dba-tech at databaseadvisors.com>
> Date: Thu, Nov-18-2004 8:39 AM
> Subject: RE: [dba-Tech] Access vs. .NET
> 
> 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.
> 
> I never actually used punched cards.  I did enter data into a vt100 
> with a
> punched card drawn on the screen were you had to enter the FORTRAN 
> syntax
> into specific columns.  YUK!
> 
> John W. Colby
> www.ColbyConsulting.com