On Wed, February 25, 2009 7:05 am, Ricardo Aráoz wrote: > Hi all, I'm performing a script through odbc (sqlexec()) against an > SQLServer engine. Connection is ok, the script consists of 6 selects > with an output of 62000, 31000, 1350000, 20000, 27000, and 14 records. > Comes back from sqlexec with no errors and the cursors "mostly" ok, but > some records in the cursors come corrupted, this is aleatory, sometimes 5 > cursors out of 6 are corrupted, sometimes only one. When I trace the > program and find a corrupted cursor, if I perform the query for that > cursor again it will come ok. I'm guessing this might be due to > multiselect queries and will be splitting the script into different > queries (one select each). Has anyone experienced this problem or can > think of a clue as to what's going on? Is it the SQL engine or VFP the > culprit? > > TIA
Sounds like a problem with the ODBC driver (although you'd think it would work fine since it's SQL Server...their own product). Your plan to split them up makes sense to me. It's the same amount of data regardless, whether you bring it back as one huge heap of 6 cursors, or 6 times of single cursors....I wouldn't expect there to be much performance difference? _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
