How to timeout a subroutine while it's running

[mcucino]

I have some slow running code and I'm trying to bypass the records in the loop causing the code to run slowly. Some of the records take 45+ minutes to calculate. Is there a way to set a timeout, where it will try to calculate the value, but if it doesn't calculate within 30 seconds, move to the next record?

Public Sub SpeedTest(Rpt As Long)
Dim rs As dao.Recordset
Dim db As dao.Database
Dim b As Date


    [TempVars]![tv_currentID] = Rpt
    RunSQL "Delete * from SpeedTestT"
    RunQuery "SPeedtestMTq"
    Set db = CurrentDb
    Set rs = db.OpenRecordset("SELECT * FROM SpeedTestT;")
    
    If Not (rs.EOF And rs.BOF) Then
        rs.MoveFirst
        Do Until rs.EOF = True
            rs.Edit
            b = Now()
            rs!starttime = b
            rs!Equals = Eval(rs![Equation])
            rs!ttc = Round((Now() - b) * 24 * 60, 5)
            rs.Update
            rs.MoveNext
        Loop
    End If
    
    rs.Close
    db.Close
    
    Set rs = Nothing
    Set db = Nothing
End Sub

[June7]

Not that I know of. Really should figure out why some records take so long to calculate.

[Micron]

According to here http://allenbrowne.com/AppIssueBadWord.html#E
Equals is a reserved word. Also, should be rs!update, not rs.Update?
Probably not the reasons why, but worth a shot. How do you know it is "some" of the records that take a long time as opposed to all of them? Or are you not referring to within a given set of records, but some sets and not others?
Also looks like you're using a function to run a query. I take it this is not just a Select query (if it is, it's probably a waste of time and resources).
I get the rs.Close, but not db.Close.

[pbaldy]

. Also, should be rs!update, not rs.Update?

I have half bottle of wine in me, but I think not. Generally, bang would refer to a field, dot to a method. The .Update "closes off" the .Edit. In other words, it commits the edited data.

[moke123]

    RunSQL "Delete * from SpeedTestT"
    RunQuery "SPeedtestMTq"

Shouldn't that be Docmd.RunSql?
I have never seen "RunQuery". Shold that be DoCmd.OpenQuery?

[orange]

Tell us about the record and calculation that is taking 45+ minutes to execute.
Do you test your proposed calculation and get it "optimized" before going to "production mode"?

[Micron]

I have never seen "RunQuery". Shold that be DoCmd.OpenQuery?

No doubt a function call as I suggested. I've used something similar before. In fact, you will find that exact procedure name in code posted elsewhere.

[moke123]

It was actually RunSql, a method, that caught my eye.