Does the "Use Declare/Fetch" option get rid of performance and other
problems with combo boxes in Access when the row source is an SQL query?
The description suggests that it retrieves up to 100 records at a time using
a cursor, without the need for any coding on the client side. Some
references (MS Access 2003 Inside Out and Programming Access 2002) suggest
avoiding combo box lookups from queries, but this could be a solution.
If so, should two separate DSNs be configured for a database in which
client-side combo boxes will be used (one with Use Declare/Fetch for combo
box queries)?
Thanks,
David P. Lurie