Hi guys,
I've found that writing data into an OLE filed used as a Blob (there's an example in the MS support center) the data written are of double size respect to the original data. If I write a 100k image for example, the fieldsize property returns 200k. When I read it from Access there's no problem, cause it reads 200k and write to disk 100k.
The problem is that using a different application to read the field, such as .NET, the data written are 200k and the image cannot be displayed.
The same happens writing with .NET and reading with access: 100k written to the field and 50k written to disk by access.
Someone knows how to avoid this problem. I've to exchange images written to a database (not to disk) between different applications.
Thanks Stevie B. Gibson
I've found that writing data into an OLE filed used as a Blob (there's an example in the MS support center) the data written are of double size respect to the original data. If I write a 100k image for example, the fieldsize property returns 200k. When I read it from Access there's no problem, cause it reads 200k and write to disk 100k.
The problem is that using a different application to read the field, such as .NET, the data written are 200k and the image cannot be displayed.
The same happens writing with .NET and reading with access: 100k written to the field and 50k written to disk by access.
Someone knows how to avoid this problem. I've to exchange images written to a database (not to disk) between different applications.
Thanks Stevie B. Gibson