Hi Marc, >> 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. :)
Fine. > I assume blocking on giving the exact size as a limit did for the same > reason, waiting for the EOF. Yes. > Well, it does only partly. I succeeded in writing to JDBC connected > databases, using ODBC didn't do, blocking as before. Fixed in CWS dba31c (too lazy to write a dedicated issue). >> (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? Yes. > Thanks for investigating and finding a solution, You're welcome. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
