[dba-Tech] Access vs. .NET

John,

>> All the end user classes should be searched, then a drill down to look at inherited stuff if you want to.  That isn't how it works, and probably never will work that way so it's all a moot point. <<

I've wondered about the organization of the "help" myself. You're right about the inheritance hierarchy. One would think that a switch could be invoked to allow the hierarchical detail to be displayed, something like the sub datasheet concept in Access. Yeah, it's a moot point, but we're the poor schmucks that have to deal with the help system.

Speaking of books, I purchased the entire Murach series on .NET development and SQL Server (Beginning Visual Basic .NET, VB.NET Database Programming w/ADO.NET, ASP.NET Web Programming w/VB.NET, and SQL for SQL Server) as well as the O'Reilly Programming ASP.NET, and the Microsoft ASP.NET Programming with Visual Basic.NET Step by Step and Web Database Development Step by Step .NET edition. How about you?

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 10:12 AM
> Subject: RE: [dba-Tech] Access vs. .NET
> 
> LOL.  Buy a book - or several.  
> 
> Someone was mentioning getting "thousands of hits" on a search of help 
> for
> some subject.  That is what I mean by too much stuff in the help 
> system.
> Yea, it is good to have it documented, but it would be nice to have it 
> not
> show up unless specifically asked for.  All the end user classes should 
> be
> searched, then a drill down to look at inherited stuff if you want to.  
> That
> isn't how it works, and probably never will work that way so it's all a 
> moo
> point.
> 
> John W. Colby
> www.ColbyConsulting.com