I am developing an application that uses an Access 2003 .adp GUI and a SQLServer database. I have read elsewhere that using subforms in the GUI will cause a performance hit because of extra unnecessary database calls. Can anyone comment on this? I have been attempting to avoid using subforms because of this but I think I need to use one because I essentially need a multi-column listbox where each of the cells is updatable rather than just read-only.
Specifically, my form contains a dropdown with a list of names. When a name is selected (AfterUpdate event), I want the subform/listbox to be populated so that individual items can be edited. I made a multi-column listbox based on a SQL query, but the data is read-only. Is a subform the only way to accomplish this and if so, any suggestions on how to keep the performance as efficient as possible?
Finally (and this is kinda unrelated so I will spread the points around if necessary), whichever display method I use (subform or some wonderful updatable listbox), I would like to populate it from a stored procedure with a parameter rather than a query since the query is somewhat wordy. If someone can point me to an example of this I would appreciate it.