The information in this article applies to:
SYMPTOMS
Creating a table with double precision for the same data field column but
in different order may result in an inconsistent table definition.
The GuessWhatCol in floatTable becomes float, which is 8 bytes in size,
while the same GuessWhatCol in realTable is real, and 4 bytes in length.
WORKAROUNDTo work around this problem, you can specify the binary precision for SQL Server 6.5, or decimal precision for SQL Server 6.0. The following sample scripts demonstrate the workaround for both SQL Server 6.0 and 6.5:
STATUSMicrosoft 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:
Keywords : kbusage SSrvTran_SQL kbbug6.50 kbbug6.00 |
Last Reviewed: December 14, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |