[AccessD] From a reader

Jim Lawrence accessd at shaw.ca
Tue Feb 8 15:42:16 CST 2011


Now you are talking... that should thin out the ranks considerable.

Jim



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Tuesday, February 08, 2011 1:12 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] From a reader

 > No one should be able to build a web site with any tool until they can
prove they can build a 
commercial site with note-pad. ;-)

Likewise an access database and a database.

;)

John W. Colby
www.ColbyConsulting.com

On 2/8/2011 3:45 PM, Jim Lawrence wrote:
> No one should be able to build a web site with any tool until they can
prove
> they can build a commercial site with note-pad. ;-)
>
> Jim
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
> Sent: Tuesday, February 08, 2011 11:30 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] From a reader
>
> The funny thing is, the reason Access gets such a bad name is that it
> can be used by amateurs, and when that happens, you get clunky.
>
> A professional Access developer understands what an .mdb is.  They
> understand the inner-workings enough to optimize performance.
>
> This is the same reason so many 'clunky' web applications have been
> made.
>
> How many Access pro's could tell you EXACTLY what Jet is doing when you
> are running 'SELECT * FROM tblSomething WHERE ID=1' against a table in a
> backend .mdb?  Probably very few.  How many could give you a conceptual
> statement as to what is happening, like 'Jet is reading the index values
> from the b/e .mdb, and then using that information to determine where to
> start reading the table data'?  Probably most.  Yet how many 'amateurs'
> have even a conceptual understanding?  They don't need to, Access just
> does things for them.
>
> Same problem with the web.  There are a WIDE variety of tools available,
> that let someone with little to no understanding of a
> website/webserver/browser system throw a 'fully functioning' (<--- term
> used very loosely) 'website' (<---also used very loosely) up into
> production.  It has been this way for a while.
>
> Drew
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
> Sent: Thursday, February 03, 2011 8:30 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] From a reader
>
> I just LOVE that word "Clunky" to describe a web app !!
>
> When everyone says how great the web is, I just point out all of the
> "clunky" webapps I have to tolerate....from my bank, to my insurance
> company, and on and on it goes. Then I get to a client site and have to
> tolerate all of THEIR clunky webapps. They are slow, they don't respond,
> they forget to validate, etc, etc., they don't integrate with windows,
> they
> don't cut-and-paste properly, and the list just goes on forever.
>
> I'm going for a long, long winternight's sleep. Someone wake me up when
> all
> clunky web apps have been upgraded to Web 2.0 standards.
>
>
>> make it 'look' like an access combobox, and act like it, but what's
>> happening in the background is clunky.  First, .Net is creating
>> javascript on the client side that is reacting to the 'OnClick' of the
>> combobox (or index changed event), then it's sending all the current
>
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list