[AccessD] Find First in an Array?

So how fast is it going and what did you do to speed it up?

John W. Colby
www.ColbyConsulting.com


Rocky Smolin at Beach Access Software wrote:
> Yeah, I think you're absolutely right - opening a recordset of only the
> controls on a form and looping once forward through the recordset filling
> the controls will be faster than the other way.  However, given how fast
> it's going now I wonder if I'll be able to see a difference.  
> 
> Right now I've got echo off while translating, resizing and maximizing the
> form.  So there's only one 'painting' of the form.  I don't know if that
> painting, which kind of proceeds from left to right and top to bottom can be
> replaced with a 'pop'.  And again, since I'm independent and my time is
> really my money, I like to go for the most economical solution and not the
> most elegant. 
> 
> Shamil asked the right question - how much time do I have for experimenting.
> Sometimes I envy those in the W-2 world.  
> 
> 
> Rocky Smolin
> Beach Access Software
> 858-259-4334
> www.e-z-mrp.com
> www.bchacc.com
>  
>  
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
> Sent: Thursday, February 19, 2009 3:44 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Find First in an Array?
> 
> Just to clarify Rocky....
> 
> While I completely agree that classes and collections provide fast, clear
> programming, with tons of capabilities, and I use them all the time from
> their abilities (which sometimes sacrifice a tad of speed for actual
> performance and ease of use).... your initial issue of using FindFirst will
> be faster with seek, but Seek is still going to have to do some looking.  
> 
> Reversing your logic, to find and fill the controls based on the record,
> instead of finding the record based on the control will go faster then
> either FindFirst or Seek.  Because there will be no 'hunting' necessary.
> The query will bring up all the info for a specific form (so you are dealing
> with less data, less overhead), and then you just run through the recordset.
> 
> If you want something that will go even faster.... create a global class,
> that loads all translations for all controls, and just keep it all in
> memory.  That is going to be more programming though.
> 
> And I doubt you will see much of a difference in performance doing the
> 'reverse logic' method over a collection method.
> 
> Drew
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
> Beach Access Software
> Sent: Thursday, February 19, 2009 4:53 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Find First in an Array?
> 
> Thank YOU!
> 
> Someone once posted I think it was on this list 'A good program is one that
> works'.  That's my motto, now.  No one ever looks under the hood, and I
> always judge my programs from the outside.  Matters not how the data got on
> the form as long as it happens 1) fast and 2) accurate.
> 
> Right now, my quest for faster translation is because I see some delay,
> especially in the Chinese  (think it may be due to the Unicode), and I'd
> like to get rid of the flashing that seems to accompany many Access apps at
> one point or another.  
> 
> Going to FindFirst to Seek seems fast and easy so the time may be worth the
> risk for an improvement in user comfort. 
> 
> However, it's a good opportunity to learn and use a class.  So I'm going to
> have to find the time to go back to the beginning to John's classes class
> and learn it.  Seems like a valuable thing to do now that retirement seems
> to have receded into the distant future.
> 
> 
> Rocky Smolin
> Beach Access Software
> 858-259-4334
> www.e-z-mrp.com
> www.bchacc.com
>  
> The information contained in this transmission is intended only for the
> person or entity to which it is addressed and may contain II-VI Proprietary
> and/or II-VI Business Sensitive material. If you are not the intended
> recipient, please contact the sender immediately and destroy the material in
> its entirety, whether electronic or hard copy. You are notified that any
> review, retransmission, copying, disclosure, dissemination, or other use of,
> or taking of any action in reliance upon this information by persons or
> entities other than the intended recipient is prohibited.
> 
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>