| Author |
 Topic  |
|
ChrmnMAO
USA
19 Posts |
 Posted - Jul 22 2014 : 09:34:49
|
Thanks Nigel,
I will package up the test project I have been working with, along with SQL Server table definition, and a sample file, so that you can take a look at it.
Also, I am open to hosting a GoToMeeting session if it would be helpful.
Thanks,
Martin |
 |
|
|
ChrmnMAO
USA
19 Posts |
Posted - Aug 05 2014 : 13:57:45
|
I am happy to say that I have found the cause of this behavior, and that the cause had to do with a dbExpress error, not an error in the ImageEn components, as I had theorized. Based on what I have read, this may only be an issue in the XE2 release.
The bug is that assigning a value of -1, which is supposed to mean no limit, does not work properly in the MaxBlobSize parameter in the TSQLConnection component and/or dbxconnections.ini file. Assigning the value of -1 to this parameter actually limits the blob size to 1Mb. Data is preserved in the first 1Mb of the data, but nulled for the remaining data (i.e., all data past the 1Mb threshold). Setting the MaxBlobSize to a specific value (I used 50000000 for 50Mbs) seems to allow all data to be saved and recalled.
An article that describes the problem as well as the solution:
http://stackoverflow.com/questions/12225450/tsqlquery-only-streams-first-1mb-of-data-correctly-for-large-strings
The following is a link to the Quality Central report:
http://qc.embarcadero.com/wc/qcmain.aspx?d=108475
Best Regards,
Martin
|
|
|
|
xequte
38603 Posts |
|
|
Topic |
|
|
|
Search
Streaming scanner-acquired images to database
