>My colleague (tester) told me she reproduced the same problem locally with 30 minute lessons. The incentive of less than .5 is still firing for them.
>
>This doesn't make much sense since the SET DECIMALS is not changed in the application and it's default VFP value.
>
>I am going to try to play with it later myself in debugging mode.

It may be that the fractional seconds portion of the VFP datetime values is not exactly .000, even though it (nominally) is in SQL Server. In that case, as you've already found you can ROUND( ) to a reasonable number of decimals, or use a fixed tolerance e.g.

* Tolerance of 0.5 seconds
IF End_Time - Start_Time > 1799.5

* Another tip - if you're working with values you suspect are not precise, performing mathematical operations
* on them makes the problem worse. Use the values directly (like the line above) rather than something like
IF ( End_Time - Start_Time ) / 3600 > 0.5