FetchAll=False and New Transaction Is Not Allowed...Error
Posted: Tue 16 Aug 2011 18:26
Hello, we have a TMSQuery with FetchAll set to False because the table has millions of records. With FetchAll=True, we get an out of memory error. With FetchAll=False, the query opens fine, however we are unable to save any changes without getting one of the following errors. We are using a TMSUpdateSQL object and cached updates. If I use MSConnection.ApplyUpdates, I get the "New transaction is not allowed because there are other threads running in the session" error. If I use TMSQuery.ApplyUpdates, I get "A trigger returned a result set and/or was running with SET NOCOUNT OFF while another outstanding result set was active. Is there any way to have MARS=True, FetchAll=False, and be able to save records without fetching all the records? Thanks, Dave