Thanks Garrett.

So, can I take it from your reply that this BUG in which "Background Data Fetch" returns duplicate rows in the resulting cursor is a well know problem? I have been using Fox since 2.5 and just discovered this recently and had seen no mention of it before. I have searched the MS knowledge base and find nothing about this.

I can reliably reproduce this error by programming in a loop to copy data from all tables in a database using SPT to select * from each table to a cursor and appending back to empty tables that have the same primary key field. It seemingly at random gets duplicate records in a selected cursor when no duplicates exist in the soruce table and the primary key index in the copy table will catch it on the append. It is like the query loses its place during the fetch or perhaps a memory leak of some kind.

I have only observed this on "select *" SPT queries on large tables using a DSN connection where BackgroundFetch = "YES", but this just tells me that this is the only place that I can "prove" that it is happening. Is there a KB article that I am overlooking? Should I report it as a bug with repro code? Can I be assured that Select * on large tables is the only place that this behavior is occuring? I am now concerned that reports that I have used for years and assumed to be correct may actually be reporting invalid data.

Thank you for any assistance you can provide. Or maybe Sergey can jump in here with his legendary searching abilities and point me in the right direction. :-)

Elmer

>>I'm not sure I understand the <*wince*> in your reply.
>
>Oh, it was just one of my least-favorite things to explain to customers when I was in PSS.
>
>>I really don't mean to cause you pain :-)
>
>Hey, why should you be different from anyone else? <*gd&r*>
>
>>But do you know if there is any workaround other than just making sure that the
>>DSN is not set to fetch data in background? Can I programatically set Fetch data
>>in background OFF before executing SPT queries in case the DSN is not properly set
>>up?
>
>Yes, I think so: I don't remember offhand how to set this for a DSN, but you can always use SQLSTRINGCONNECT() instead, and pass the "BackgroundFetch=No" clause in as part of the connection string.