DWUTKA at marlow.com
DWUTKA at marlow.com
Fri Nov 3 14:24:42 CST 2006
Build a collection, pull the records once to fill the collection, then populate the combos from a Callback function (which would get the data from the collection, vs. the recordset) Drew -----Original Message----- From: McGillivray, Don [IT] [mailto:Donald.A.McGillivray at sprint.com] Sent: Thursday, November 02, 2006 3:21 PM To: Access Developers discussion and problem solving Subject: [AccessD] Strategies for populating combo boxes Hello, All I am working on a project where I've been asked to provide an interface that allows users to choose selection criteria from a series of combo boxes and use the results to open one of six reports. This is a fairly simple database - one table with about 20 columns and 1.1 million rows. They have already built the queries and reports; all they want me to do is provide an easy way to specify selection criteria for the reports. Since there is only a single table, building rowsources for the combo boxes requires running summary queries against the various columns for all 1.1 million rows. With 6 to 10 combo boxes on the form, that creates quite a bit of hang time waiting for the combos to populate. I'm considering strategies for reducing the delay, one being to populate a series of temp tables at DB open that can be used to populate the combos. That way the big delay happens only once upon DB start, and the UI should respond more quickly. I also thought of populating a single temp table with two columns - one to identify the combo box in which the values will be used, and the other with the values themselves. I seek guidance from the experts. Are either of these ideas worthy of pursuit? Is there a better way to get there from here? Any and all comments, critiques, ideas welcome. Thanks! Don McGillivray -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com