CTT*.tmp files in c:\temp grows until 'Unable to write to file buffer' error

[Henrik Nordberg]

Hi All,

Using ODBC/CRecordset (VC++ 6/SP3;NT4/SP6a) I am trying to update a row in a SQL Server database. Getting the data is no problem,
but the Update() call fails with:

"General error: Unable to write to file buffer
[State:S1000,Native:0,Origin:[Microsoft][ODBC Cursor Library]]."

after taking a few moments to eat up all disk space of my c drive, by creating a huge CTTxx.tmp file in c:\temp.

This is code that "used to work". I changed to using OLE DB, but now I want to go back to ODBC to compare performance and other
things.

could anyone shed some light on this please?

Thanks, Henrik
_______________________________________
Henrik Nordberg hen...@commerceroute.com
Director of Research and Development
CommerceRoute, Inc. +1 510 601 6061 x107

[John Hobson]

I've seen cases where the Cursor Library reads the entire result set into a temporary file when you do an update. The Cursor Library
does this because SQL Server limits you to one active statement per connection. To issue the update, you need a second active
statement. So the Cursor Library reads the entire result set into a file so the Cursor Library can close down the original SELECT
statement.

I hope this helps. Good luck.

Henrik Nordberg wrote in message ...