>>My Access app now has Access 97 and Access 2002 interfaces, linked to tables in Access 97 over a WAN. This one big form has slowed to a crawl, so I'm trying to employ some client-server design principles as described in the Access 97/2002 Developer's Handbooks. One of those principles says that if you have listboxes, make sure the rowsource is the same as the form recordsource, so you aren't opening the table twice. My form's recordsource is a SQL statement with a dynamically generated WHERE condition (which used to go in the .FilterOn property. How do I make my two listboxes use that same cursor? This form is used for data editing, so the cursor needs to be updateable.
>
>Don't forget to post the solution here, when you find one.
>The only solution I can think of is to check Where conditions and make sure that tables have indices to speed up the data retrieval.

There are many things like that to consider when optimizing the form. My specific question for the moment is how to make the listboxes use the form's cursor rather than opening their own, if possible. In general, I am looking for the most efficient way to make them. The two listboxes list groups of fields for several records. The (single) form containing them shows all fields and navigates the same set of records. The listboxes and detail controls are hidden in pageframes. Instantiating the listboxes late is a possibility, but may not help much since the users are prone to flip the pages immediately.