SBO B1 2005 SP 01 Patch 11 - Issues with recordsets.

Question

Hi,
We are using ‘recordset’ for Query all over our application. I have performance problems when I upgraded to SP01 Patch 11. Recordset retrieves the data fast but takes very very long time when I do movenext() or eof() or movefirst().
Here is a sample code:
Dim rs As SAPbobsCOM.Recordset = Query (sqlStmt)
            ' If no record is fetched, returns false which indicates the finding failed
            rs.MoveFirst()
            If rs.EoF() Then Return False
            ' Caches the object columns
            CacheColumns(rs)
            ' Releases the referenced object
            rs = Nothing
The whole process takes long time. So I debugged the code. The delay is at MoveFirst() and eof() stage. If I comment these 2 steps, it is faster. But I have to use the recordset functions. 
IT WAS VERY QUICK IN SBO 2005 before upgrading the sp01 patch 11. Am I missing something? Is something changed in SP01? I am using Recordset to query on user tables only.
Please somebody help me out.
Regards,
Prakash

Answer 1

Does this bug also affect the GetByKey method? Because I am developing an addon, and all of a sudden it starts to hang. I did upgrade to PL11 during the development. I have been going insane trying to figure out what made my program stop working, and I even back-tracked numerous revisions. In the end, it is the following code that made the difference:
oDocs = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oOrders)
                        strSQL = "Select DocEntry from ORDR where DocNum = '" + strDocNum + "'"
oRecs = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)
                    oRecs.DoQuery(strSQL)
                    strDocEntry = oRecs.Fields.Item("DocEntry").Value
                    If oDocs.GetByKey(strDocEntry) Then
oDocs.UserFields.Fields.Item("U_MyField").Value = strValue
end if
If I comment out the last if statement with GetByKey, it seems to be fine. If I leave it in, it hangs when I click the "Update" button on the Sales Order form. The database I'm working on has thousands of order records. Could it be caused by the bug since it's a large volume of records to go through? We also use record sets all over the place. It also doesn't make sense to me that in other areas it seems to work ok.