>Hi Mike
>
>>Ummmmm Terry
>>
>>I'm really against the idea of accessing properties directly in such a fashion.
>
>Well I fell foul of using form props in SQL years ago and always assign them to a var in such.
>
>It just so happens that I suspected similar here and had already assigned it to a var and tried that, to no avail. It seems my problems stem from having that Days_Op as part of the copmposite key on which the table was ordered, as I explained. Although I can't see why the file ptr should have moved, when I hadn't changed the value of Days_Op. I have no access methods on the prop. so no side-effects as you pointed out. Besides, in debug I would have caught that happening.>

Hi Terry,
Day_op being part of composite index would not throw you to eof() when keypart value changes. Pointer would stay on the same record, but that record would be diffrently positioned twds other records according to active index.
It was active parent relationship to it that was doing it I think.

Glad you sorted it out :)