blob string

[jennid]

We have a table in our open edge database that contains a blob field (binary large object). A sister company of ours has an SQL application that reads this field. After upgrading to OpenEdge 10.2B (from 10.0C), they are having problems reading the data in the field. The code on their side takes the hexdec string of data from the blob field and converts it to a string field. In an effort to trouble shoot the problem, the developer in the SQL environment wants me to verify that the hex string he's seeing (which looks something like "202031303230333138344E444F2020202020203333393138353233303033202020324348412020202020202020363031353136203930303030342" )is the correct hex string. How can I view this string in the OpenEdge environment (either the appbuilder or even the old character progress editor)? By using the copy-lob function, I can view the actual data in the blob field, but he wants me to verify that the hex string he sees on his side is correct. How do I do that?

Thanks.

Jenni

 

[medu]

you can't display binary data in progress client, just copy-lob from your field to a file and open that file in a hex editor (http://www.physics.ohio-state.edu/~prewett/hexedit/)

 

[jennid]

Is anyone aware of any differences in how the blob data would be handled differently in 10.2B OpenEdge versus 10.0C? We set up the new ODBC drivers for the 10.2B environment and it appears that the developer that is reading the data from the blob field sees all of the data up until the 1024th byte. After that, some (but not all) of the data is being dropped...the data is definitely there in the OpenEdge database, as I can view it in the OpenEdge environment, but he can't see it when connecting via ODBC. I noticed there is a new checkbox on the 10.2B ODBC driver setup labeled "use wide character types"...we tried checking that but didn't see any different results.