![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, I am using SQLPutData() in a loop to move a large BLOB (3MB in total) to and from the database and when I retrieve the BLOB I find that a large section of data has been replaced with the "BAADF00D" data sequence. This is used in many cases to init memory, including, I believe, by XP to init the Heap. Whatever the source, my data is getting trashed and I suspect it may be caused by processing too much data in a single call to SQLPutData() because this problem is occurring when I transfer 128k blocks of data in a single call to SQLPutData() but disappears when I only transfer 32k at a time I cannot find any information on SQLPutData() that discusses a maximum buffer size that can be transferred in a single call, yet I suspect that there must be a limit. Can anyone point me to some documentation that specifies a limit? Thanks, Al Koch AlKoch (AT) MyRealBoxREMOVEALLTHESECHARS (DOT) com |
![]() |
| Thread Tools | |
| Display Modes | |
| |