The first thing I will add is to make sure you use the reset="true" parameter in your <cfcontent...> tag. Otherwise any white space in your CFML file will be include in the response sent to the client throwing off any binary content you are trying to deliver. With text based content like HTML extra whitespace is seldom a problem. But binary data cares about every single byte sent.
Yea, sorry, I actually do have that attribute defined within cfcontent. I just didn't transfer over the code properly in my forum posting. The error I'm focusing on is ByteArray objects cannot be converted to strings.
Some additional background info:
CF 8.0.1, db is mssql
The error I'm focusing on is ByteArray objects cannot be converted to strings.
That type of error generally means you are passing binary data into a function/tag when it expects a string.
<cfcontent type="#sMime#" file="#qGetImage.ImageFile#">
If qGetImage.ImageFile contains binary data, use cfcontent's "variable" attribute instead. The "file" attribute is used when you are referencing a physical file, and the value would be a path like c:\somefolder\myImageName.jpg.
You should also verify that the "Enable binary large object retrieval (BLOB)" option is checked for your CF datasource.
oh man, that was one of those "holy crap, are you kidding me moments!?"
Thank you so much! I can't believe I forgot and/or didn't read into the cfcontent issue.