cancel
Showing results for 
Search instead for 
Did you mean: 

Time Out/Record Lock - Recordset

Former Member
0 Kudos

Hi all,

we are using ADO(VB6) and SAP Recordset in 'mixed' mode in our AddOn.

Since we installed 2005 SP01 PL11, we have strange problems with TimeOuts/Record Locks. For example, after reading highest number from AddOn-table over SAPbobsCOM.Recordset, the table has locks.

They are visisble in SQL Server Enterprise Manager.

If we want to Update/Insert/Remove Data over ADO in a following task, an ODBC Time Out occurs.

Has anybody an idea ?

Thanks in advance

Thomas

Accepted Solutions (1)

Accepted Solutions (1)

barend_morkel2
Active Contributor
0 Kudos

Hi Thomas,

I don't know what's causing this, but here's a suggestion: Why don't you just use the SAPBobsCOM.Recordset Object (connected by the Company Object). This should not cause any issues. What you could do as a precaution is to kill the recordset object (set to nothing) after using it and call the Garbage Collector - This will release the handle/lock to the DB.

Former Member
0 Kudos

Hi Barend,

thanks for your tip, but unfortunately we need the ADO Recordset in some cases, and that AddOn also is developed in VB6, there's no Garbage Collector.

Thomas

barend_morkel2
Active Contributor
0 Kudos

Hi Thomas,

If there is no garbage collecter, there should be some maechanism to release objects. You must apply this or else the object will keep its libk to the table and/or record set and this will cause the lock issue.

Answers (0)