Am Donnerstag, den 18.09.2008, 13:15 +0200 schrieb Frank Schönheit: > The proper macro has an additional "oPipe.closeOutput" right after > writing the document into the pipe, but before passing the pipe to > setBinaryStream.
That does work. :) I assume blocking on giving the exact size as a limit did for the same reason, waiting for the EOF. Well, it does only partly. I succeeded in writing to JDBC connected databases, using ODBC didn't do, blocking as before. But this clearly is a "works for me"-remark currently. > (Strictly, the implementation of setBinaryStream for the dBase driver is > broken, as it does *not* do what your macro requests it to do.) Because it doesn't start reading on a stream that hasn't finished getting all data from the writing end? Thanks for investigating and finding a solution, Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
