[AccessD] Performance tips anyone?

Damn, who brought up bound vs unbound again?  They need taken out back and
beatin.

Reuben Cummings
GFC, LLC
812.523.1017


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of jwcolby
> Sent: Thursday, July 05, 2007 1:32 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Performance tips anyone?
>
>
> Drew,
>
> >But Access is just as well suited for unbound solutions too.
>
> Just as well suited as what?  Access is NOT as well suited for
> unbound as it
> is for bound.  Access just has TONS of features in it directly
> dependent on
> bound forms and controls.  Unbounders throw all that stuff away;
> To try and
> implement that stuff in an unbound solution requires a LOT of custom code.
> AFAICT most Access "unbounders" make no effort to recreate most of what
> Access just "gives" us bounders.
>
> And Access is certainly NOT as well suited for unbound as VB.Net
> (or even VB
> 6), not that I am an expert in .Net yet.  But you are talking a
> whole nother
> ball game when you talk .Net.
>
> So as much as I love ya, I have to disagree with that one.  I
> think you are
> one of the "been doing Access unbound so long you forgot the pain" folk.
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
> Sent: Thursday, July 05, 2007 1:16 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Performance tips anyone?
>
> But Access is just as well suited for unbound solutions too.  The only
> exception to that rule is it's goofiness with callback routines. (Can't go
> into debug if you have a callback routine ANYWHERE.  Goes haywire).
>
> Drew
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Thursday, July 05, 2007 11:30 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Performance tips anyone?
>
> Jim,
>
> >You mentioning this will not cause near the stir as it did 10 years ago
> as
> most (all?) have now accepted the reality. ;-)
>
> LOL, no not quite.  Access is a tool built from the ground up for bound.
> To
> even discuss unbound for Access NOW, when much more robust
> unbound tools are
> available is ... well... kinda silly.  Unless of course you have
> been doing
> unbound with Access for the last 10 years in which case you have the
> expertise to do so.  Telling the average Access nubee to use
> Access unbound
> is IMHO a disservice to the nubee.  He might as well just go learn VB.Net.
>
> As for me, if I need unbound it will be in VB.Net, NOT in Access (and I am
> not an Access nubee).
>
> The right tool for the job so to speak.
>
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
> Sent: Thursday, July 05, 2007 12:13 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Performance tips anyone?
>
> Yes, Drew you have hit on the key to performance... 'unbound'.
>
> You mentioning this will not cause near the stir as it did 10 years ago as
> most (all?) have now accepted the reality. ;-)
>
> Jim
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>