Robert

>> Is it possible that you have set a filter on the table that did not get
>> removed? That could explain the sporadic problem, it would appear only when
>> the filter is on, so it would depend on what the user did before this
>>function. You could do a search on all the programs for table.filter.

I really apreciate your concern but this is not the case. I *never* use filters and I am pretty sure the fields that
belongs to the range were not changed. Last night I've verified the table and it shows me nothing. After that I
repair the table and now I am just waiting to the problem occur again.

Eduardo

Eduardo,

<< The fields changed doesn't belong to the range neither to the index key
and therefore any changes can't alter the order of TIno. >>

Just a thought - any Refresh done to the dataset (or any record pointer
movement that moves the record pointer off of EOF) will cause BOF and EOF to
get reset.  Is there a chance that some event handler, etc. is moving the
record pointer ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

> Just a thought - any Refresh done to the dataset (or any record pointer
> movement that moves the record pointer off of EOF) will cause BOF and EOF
> to get reset.  Is there a chance that some event handler, etc. is moving
> the record pointer ?

No, I will try to replicate the problem or even check my code again but this
is a simple routine that occurs after printing.

Eduardo