I've upgraded an Access 2003 application to Access 2016 and migrated it's back-end to SQL Server.
I'm experiencing lockups on a particular form which features ~25K records.
Upon running an SQL Server Profiler trace, I noticed that for every row returned by query, an
Form Record Source:
I tried a few suggestions I found while Googling the issue, to no avail: removing the
I don't necessarily want to get rid of
Is there any way to keep
Does anyone know why
Thanks in advance!
I'm experiencing lockups on a particular form which features ~25K records.
Upon running an SQL Server Profiler trace, I noticed that for every row returned by query, an
sp_execute
query is also being invoked.Form Record Source:
SQL:
SELECT PileInfoMain.Batch, PileInfoMain.Stake, PileInfoMain.WasteStream, PileInfoMain.DateStaged, PileInfoMain.SpecialStatus, PileInfoMain.CurrentStatus, PileInfoMain.Comment
FROM PileInfoMain
WHERE (((PileInfoMain.CurrentStatus)="DONE"))
ORDER BY PileInfoMain.Batch;
I tried a few suggestions I found while Googling the issue, to no avail: removing the
WHERE
clause, removing the ORDER BY
clause, and making the query pass-through. Finally, I changed the form's Recordset Type
from Dynaset
to Snapshot
and the sp_execute
queries disappeared.I don't necessarily want to get rid of
Dynaset
because I want changes made by other users to be reflected without closing and reopening the form.Is there any way to keep
Dynaset
without the extraneous sp_execute
queries?Does anyone know why
Dynaset
causes all of these sp_execute
queries?Thanks in advance!