BUG: SqlRpcParam%() Failed with "YYYY/MM/DD HH:MM" Parameter

 Last reviewed: April 8, 1997
Article ID: Q152619
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5

SYMPTOMS

When you attempt to specify a string of a datetime as a parameter in an remote stored procedure (RPC) execution, error message 10039 appears: 

   Attempt to convert stopped by syntax error in source field.

CAUSE

The function SqlRpcParam rejects attempts to specify a datetime parameter if the datetime string used as the remote stored procedure parameter is in "YYYY/MM/DD HH:MM" format.

WORKAROUND

There are two possible workarounds for this problem.

  • Instead of using SQLDATETIME, use SQLCHAR as the datatype of the datetime string parameter.

-or-
  • Use the date string in different format.

STATUS

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

Additional query words:
Keywords : kbbug6.00 kbbug6.50 SSrvDB_Lib SSrvProg
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 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.