Combo Box and SQL

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Our application uses a msaccess frontend and a mssql backend (linked tables).
Our application occasionally experiences blocking in sql.

We have identified a situation with the combo boxes. When the rowsource of
the combo box is large the sql2005 activity monitor shows “Suspended†in the
status column. In other words, sql does not complete the query. If you scroll
to the end of the list in the combo box the process will complete. If you run
the rowsource query outside of the combo box the sql process completes.

From what we can tell these “Suspended†processes are occasionally causing
blocking.

Does anyone know why the processes don't finish? Recommendations.
 
James said:
Our application uses a msaccess frontend and a mssql backend (linked
tables). Our application occasionally experiences blocking in sql.

We have identified a situation with the combo boxes. When the
rowsource of the combo box is large the sql2005 activity monitor
shows "Suspended" in the status column. In other words, sql does not
complete the query. If you scroll to the end of the list in the combo
box the process will complete. If you run the rowsource query outside
of the combo box the sql process completes.

From what we can tell these "Suspended" processes are occasionally
causing blocking.

Does anyone know why the processes don't finish? Recommendations.

That is standard behavior, not to retrieve all records for a CombBox or ListBox
until the user scrolls to the end. If you execute code...

SomeVar = Me!ComboBoxName.ListCount

....that will force the control to retrieve the entire list and release the lock.
This could introduce a delay when you run the code though if the list is long.
 
Rick Brandt said:
That is standard behavior, not to retrieve all records for a CombBox or ListBox
until the user scrolls to the end. If you execute code...

SomeVar = Me!ComboBoxName.ListCount

....that will force the control to retrieve the entire list and release the lock.
This could introduce a delay when you run the code though if the list is long.

WOW! Worked Great. Thank you very much.
 
Back
Top