Hi dragan,

>I agree - and Fabio is very good for that because he obviously knows Fox very well, but doesn't have the decade of habits like many of us do, so he doesn't follow the well beaten paths. Instead, he tries everything - and finds things we'd never find.

>He's also very thorough. I know that when I find a behavior in Fox, I don't poke it from so many angles - I rather try to find a workaround as fast as I can, and pinch another little flag into my bug map. But he does try everything - and diligently posts here. Admirable.

Well, I certainly do poke it from various angles if the BUG is difficult to circumvent. I work a lot with grids and you'll find that I've posted quite a few problems with grids. However, if a bug is difficult to reproduce and I can solve the problem another way, I don't take the time to find this stuff out to the extend Fabio does. I really don't have the time for that. Therefore I do have a lot of respect of what Fabio is doing here.


Example of a problem I found yesterdaqy which probably is a bug, but could not make repro code. In a grid in the AfterRowColchange

SELECT SomeTable
IF !EOF() AND RECNO() > 0
    GO RECNO() IN someTable  && Errors with Record out of range.
ENDIF

No filters in effect, One active non filtered index, via the debugger I found no other code running besides this, but it was erroring on a newly added record (Tablebuffered). I spend two hours to find the exect cause, but eventually found a workarround to the problem.

I really feel that the VFPT should do something about these bugs because they make my life as Developer miserable. I probably spend 1/3 rd of my programming time in dealing with issues related to BUGs. And If you asked me that is far too much...

Walter,