I removed the PictureEdit control from the form.
...here's where it gets embarassing...
I added the SF PictureEdit control. Everything works beautifully! Just like I expected it to.
The problem stemmed from me having a newer version of the controls and I was too lazy when I first created the window to download the older version (DevEx 6.3.3). In order to get the images to show up (not store), I used a BusinessBindingSource on the newer versioned PictureEdit control. While it worked to show an image properly, it would not save it.
So, lesson learned. Don't use a hammer and chisel to get the food out of your teeth, use a toothpick!
Bill
Got more work to do on this.
public
I see now how the byte[] type is converted to a bitmap type. Cool. I am now following the code through to test the PictureEdit control on my form. I have to tie up a few loose ends, first, though.
I have read through those posts. I get an conversion error during compile that states that I am unable to convert from the byte[] type to the image type. Not sure how the first post actually works when substituting the null value with the CType function. Also, the whole concept of serializing the data doesn't seem quite appropriate in this situation. The data flows beautifully from the database to the control (not serialized). It is just the reverse that seems to be the issue. I cannot change the image and persist it to the database. The second thread suggest that the data be re-typed at the BO level (?) and serialized. Well, wouldn't I get the same error if I tried to make a bitmap out of a byte[]? The third thread comes across as Martian to me. Sorry.
Any thoughts on what that "extra step" might be? Sure would be nice to save images by simply binding the field to the control...like all other controls (textedit, comboedit, etc.).
Thanks a lot for the help, Greg!Bill
Any ideas?
Thanks!Bill