It's not very probable, but Denis could be using the non sql version of INSERT. And then, if he is not setting the right SELECT, he might be inserting in another table, without generating an error. Admittedly it's a long shot.


>I might be proven wrong, but I think that INSERT INTO always inserts a record (you don't have to be at the target area to make it work - in fact, the target table does not even need to be in use). It's things like REPLACE that... hmm... "fail" at EOF().
>
>>>Denis, I think you should really provide some code here... Does not need to be your exact code, but at least one that can reproduce the outcome.
>>>
>>>I tried to follow the description of your scenario:
>>>

>>>[...]
>>>INSERT INTO curReport VALUES (curTable.someField)
>>>

>>>
>>>Does this represents what you are doing or am I missing any piece?
>>
>>If that's the case, this could be one of the cases when things stop working when you're sitting on an alias which is at eof(). Just moving to a real record should then make it work.
>>
>>OTOH, if he's inserting from variables... perhaps the solution would be the same, or I'd be scratching my head just like he is.