>Here is the section where the parameters that are sent to the stored procedures are set up.
>
>....
>.Parameters.Add(myDataBaseProvider.CreateParameter("@tRespDate", _response))
>.Parameters.Add(myDataBaseProvider.CreateParameter("@tXML", _xML))
>.Parameters.Add(myDataBaseProvider.CreateParameter("@tSignature", IIf(buffer Is Nothing, DBNull.Value, buffer), DbType.Binary))
>
>The third parameter is an image that's been converted to a binary stream. At this point the value of "buffer" is correct and contains the binary data. This is sent to a VFP store parameter that creates a new record and saves the data. This signature field in the VFP table is a blob field that accepts null values.
>
>The stored procedure looks like this:
>
>PROCEDURE AddRespArch
>LPARAMETERS theNewID AS INTEGER, ;
> tPatID AS INTEGER, ;
> tRespDate AS DATETIME, ;
> tXml as String, ;
> tSignature as Image
>
>LOCAL newresparchid AS INTEGER
>
>NewID('RespArch','iresparchid',1,@newresparchid)
>
> INSERT INTO RespArch ;
> ( ;
> iresparchid, ;
> ipatientid, ;
> tresponse, ;
> xml, ;
> bsignature ;
> ) ;
> VALUES ;
> ( ;
> newresparchid, ;
> tPatID, ;
> tRespDate, ;
> tXml, ;
> tSignature ;
> )
> theNewID = newresparchid
> RETURN GetNewIDResSet(theNewID)
>ENDPROC
>>
>
>If the value of tSignature is tested immediately after the LPARAMETERS statement, it always NULL, the other values are correct.
You're right. Looks like a bug in VFPOLEDB.
Cetin
