Re: Appendchunk/Update of varbinary column fails on ODBC Linked table?
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Tue, 10 Jun 2008 18:58:07 -0500
<ash.sozoh@xxxxxxxxx> wrote in message
news:fcf07548-c57d-4eb6-b5a9-9253c0dea5bd@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a varbinary(max) column in a SQL Server table. I am trying to<snipped code>
populate it through VBA code.
The code fails when the update to this column is done with a large
file and in a linked table environment in MS Access.
The linking is done using an ODBC system DSN. It is interesting that
the code works fine with smaller files.
So, the question is, is there a limit on varbinary columns supported
through ODBC? If no then how I can fix the error. I will appreciate
the help.
Ash
Take a look at this article: http://support.microsoft.com/kb/194975
One of the suggestions is to use OLE DB instead of ODBC drivers if you
experience problems. Another is to Select individual fields, not "*", and
always Select the BLOB columns last.
AddChunk and GetChunk have always been an adventure with DAO and ADO, with
odd behavior between different configurations the Norm, not the exception.
<g>
-ralph
.
- References:
- Appendchunk/Update of varbinary column fails on ODBC Linked table?
- From: ash . sozoh
- Appendchunk/Update of varbinary column fails on ODBC Linked table?
- Prev by Date: Appendchunk/Update of varbinary column fails on ODBC Linked table?
- Next by Date: ADO returns empty recordset sporadically under Interop scenarios
- Previous by thread: Appendchunk/Update of varbinary column fails on ODBC Linked table?
- Next by thread: ADO returns empty recordset sporadically under Interop scenarios
- Index(es):
Relevant Pages
|