D
Domac
Hi,
I am using SQL Server 2000 as backend, where I store files, so i came to
problem when I fill IMAGE (OLE Object) field with files larger tha 50 mb.
Table is linked to access 97 application, i use DAO GetChunk and AppendChunk
methods.
Error (ODBC call failed) emerges when I call Update method of recordset
object.
I've run some tests with same table structure using access97 db as backend
and everything works fine, files of 150 mb are 'uploaded' without problem.
When I use SQL Server 2000 as backend , i can't insert more than 50mb into
field.
What is the problem?
Cache between access and Sql server?
Is DAO adept for such operations?
SQL Server documentation states that IMAGE type fields (witch translates as
OLE Object on 'Access' side ) can store up to 2GB.
I am using SQL Server 2000 as backend, where I store files, so i came to
problem when I fill IMAGE (OLE Object) field with files larger tha 50 mb.
Table is linked to access 97 application, i use DAO GetChunk and AppendChunk
methods.
Error (ODBC call failed) emerges when I call Update method of recordset
object.
I've run some tests with same table structure using access97 db as backend
and everything works fine, files of 150 mb are 'uploaded' without problem.
When I use SQL Server 2000 as backend , i can't insert more than 50mb into
field.
What is the problem?
Cache between access and Sql server?
Is DAO adept for such operations?
SQL Server documentation states that IMAGE type fields (witch translates as
OLE Object on 'Access' side ) can store up to 2GB.