BUG: Linked Table Shows Incorrect Field Size

Last reviewed: April 10, 1997
Article ID: Q163894
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 11462 (WINDOWS: 6.0, 6.5)

SYMPTOMS

Sp_columns returns incorrect information regarding the precision of fields in a view if the fields are concatenated, calculated, or derived. If Microsoft Access links to such a table, it receives incorrect information regarding the size of the field. Tables created from linked tables with a Make Table query in Microsoft Access truncate the data.

CAUSE

When a view is created, it correctly adds the lengths of the fields together, but it uses the precision of the first field named in the concatenation. Fields in the view that are calculated or converted from other datatypes may also show incorrect precision. When Microsoft Access links to a view and queries sp_columns, it receives incorrect information about the column.

WORKAROUND

To copy a linked table while in Microsoft Access, create a new table structure in Microsoft Access with the fields set to the correct size. Use an append query to move the data from the linked table to the new table.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: attach attached import
Keywords : kbbug6.00 kbbug6.50 kbinterop kbusage SSrvGen
Version : 6.0 6.5
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.