>>>I have a button within a pageframe that has a lot of code in it's click method. Including some rather lengthy select statments. The problem is when I try to trace through the code the debugger will only go so far then it will stop tracing. Every time I hit F8 in the debugger it continues to execute the next line it just won't show what line it's executing. This makes it really hard to debug.
>>>
>>
>>I'm not sure what could be happening here. If you think that this is a bug, you need to try and reduce the problem to as few lines as possible that will still reproduce it. Then you need to make sure that it happens on other forms and other machines. It is extremely difficult (impossible?) for anyone here to try and determine what the cause of this might be without knowing more specifics, and without having steps to reproduce the problem.
>>
>>
>>>VFP didn't seem to be filling the _tally variable correctly at this point. Although the select statement selected 0 records the _tally variable seemed to hold the value from the select statement above this one.
>>
>>
>>_TALLY has a couple of quirks that makes it undependable at times, and this is one of them. To be safe, just check the existence of the first element of the array first, or when selecting into a cursor, check RECCOUNT().
>
>Thanks for the advice. I'll definatly try to reproduce the problem per your suggestions. And I'll also stop using _tally. I just hope it isn't to unrealiable because I've used it alot.

---

I also hit quirks of _tally especially with non-machine collating sequences. As an addition to Erik, also make sure that laArray is released before SQL. Otherwise if it's already populated and SQL returns nothing you'd get previous content and think SQL returned something (no problem if SQL is part of a routine where laArray is initialized and scoped to).
Cetin
Cetin