[AccessD] more on early versus late binding

That depends on the class of machine the app runs on.  A momentary delay
on a fast machine is no big deal, but if your form has a LOT of combos
and listboxes populated that way, it can be a noticeable annoyance.  I
dealt with a situation like this by creating several stored queries and
swapping them out as the rowsource of a combobox in code to avoid the
delay that otherwise occured when loading an unbound form.

Charlotte Foust

-----Original Message-----
From: Susan Harkins [mailto:ssharkins at bellsouth.net] 
Sent: Wednesday, July 14, 2004 1:30 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] more on early versus late binding


That's exactly the problem -- it just isn't slow enough for me to bother
with -- but I can see how several spots like this would annoy a user. 

Susan H. 

Susan,

Your listbox sounds like it might be based on a select statement in its
rowsource property.  You can speed it up by switching to a saved query
and swapping out queries or paramters if you need to in order to change
the list contents.  A select statement gets compiled the first time you
run it in a session.  That takes a while.  After that, it stays compiled
for the rest of the session.


-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com