I have been chasing this bug for a week and i can't seem to get anywhere. Maybe someone has some ideas?
This is part of a quite involved process of converting and importing data to a SQL Server 6.5 table. Right now each load (one record worth of data) takes about 60 secs. to import. 45 secs. of that is spent evaluating the line between the ***** This Line ****** markers. This doesnt make any sense. This recordset is opened as a firehose cursor and so far in my testing it has returned no records. How can it take 45 seconds to see that .EOF and .BOF are true? This problem only occurs on one of my test systems, but i cant find a cause for it. Any ideas? I'm about ready to set this computer on fire, maybe that will help. This exact same type of operation is executed probably 20 other times in the course of importing a load and none of those take longer than a couple of milliseconds. Please help if you can think of anything.
TIA
Ruairi
Could your manufacturing facility benefit from real time process monitoring? Would you like your employees to be able to see up to the minute goal and actual production?
For innovative, low cost solutions check out my website.
Code:
Dim YTrs As ADODB.Recordset
Dim LogsRs As ADODB.Recordset
Dim sql As String
Dim Rec As Long
Rec = -1
If Not rescflag Then
If Val(yardticket) <> 0 Then
StartTime = Time
Open "c:\queries.txt" For Append As #55
Print #55, "STARTING: " & Format(Time, "Long Time")
Close #55
sql = "select rec from loads where yardticket = '" & yardticket & "' and destinationrec = " & destinationrec & " and (c) and (d)"
OpenSubs.OpenForwardRecordset YTrs, sql
Open "c:\queries.txt" For Append As #55
Print #55, sql
Print #55, "FINISHING: " & Format(Time, "Long Time")
******** This Line ********
If YTrs.BOF And YTrs.EOF Then
******** This Line ********
Rec = -1
Else
Rec = YTrs("rec")
End If
Print #55, "VALUE OF REC SET: " & Format(Time, "Long Time")
OpenSubs.CloseRecordset YTrs
Print #55, "RECORDSET CLOSED : " & Format(Time, "Long Time")
Close #55
EndTime = Time
Print #100, "FINDLOAD:yardtic
This is part of a quite involved process of converting and importing data to a SQL Server 6.5 table. Right now each load (one record worth of data) takes about 60 secs. to import. 45 secs. of that is spent evaluating the line between the ***** This Line ****** markers. This doesnt make any sense. This recordset is opened as a firehose cursor and so far in my testing it has returned no records. How can it take 45 seconds to see that .EOF and .BOF are true? This problem only occurs on one of my test systems, but i cant find a cause for it. Any ideas? I'm about ready to set this computer on fire, maybe that will help. This exact same type of operation is executed probably 20 other times in the course of importing a load and none of those take longer than a couple of milliseconds. Please help if you can think of anything.
TIA
Ruairi
Could your manufacturing facility benefit from real time process monitoring? Would you like your employees to be able to see up to the minute goal and actual production?
For innovative, low cost solutions check out my website.