I am contractor doing programming work for the BC Government in Canada. We have started to move from Oracle to SQL 2005 in some of our newest applications. So, our SQL 2005 server software is pretty much new... no more than 2 months old.We are migrating an application from Access 2003 to VB.Net... however that will occur in phases... on this phase we're making modifications on an access 2003 application so we can move its data to SQL 2005 SQL Server - the application will stay in Access 2003 for a short time though... Here's the problem... We were initially saving image files (.bmp) using an ADODB.Stream into a linked table field (showing the field as of binary type (510 of size) although on SQL 2005 was an IMAGE data type), and that was just working fine...However, after finding warnings in different articles of MSDN...--- e.g.: ---------Important: The image data type will be removed in a future version of Microsoft SQL Server. Avoid using this data type in new development work, and plan to modify applications that currently use them. Use the varbinary(max) data type instead. ---... We decided to apply the recommended change and turned the field into an varbinary(MAX) on SQL 2005. On the linked tables it still shows as a binary data type with 510 of size... however we cannot save the image file any more now that we have done such a change. We are getting the following error information:---Error 3163 - The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data.---Note that we are using an ODBC connection with an SQL Native Client Driver just for the sake of security reasons as we work with Windows Authentication, Active directory and all... The file sizes are in the range of 10 to 20 KB.