Problems writing table in SQL Server

Author: parcaya@compuamerica.com.ve (parcaya)

The table has fields defined as "SMALLDATETIME" and "TIMESTAMP", I cannot write SQL Server returns an error of date. Does anyone have any idea how to solve it? Thank you

4 Comments

  1. Which version of SQL Server and more specifically which ODBC driver are you using (to connect from Uniface to the SQL Server database)?

    There is a known issue when using SQL Server Native Client 10.0 for SQL Server 2008 and trying to store values (other than null) in a "smalldatetime" field. For details see (e.g.):

    Hope this helps.

    Kind regards,

    Daniel Iseli Uniface Technical Support


    Author: diseli (daniel.iseli@uniface.com)
  2. Sorry but did not work. Any ideas? Thanks for you attention


    Author: parcaya (parcaya@compuamerica.com.ve)
  3. Sorry I did not send the sqlserver information: Microsoft SQL Server Management Studio 10.50.6000.34 Microsoft Analysis Services Client Tools 10.50.6000.34 Microsoft Data Access Components (MDAC) 10.0.10240.16384 Microsoft MSXML 3.0 6.0 Microsoft Internet Explorer 9.11.10240.16384 Microsoft .NET Framework 2.0.50727.8669 Operating System 6.3.10240 SQL Native Client                          2005.90.3042.00        SQLNCLI.DDL SQL Server                                 10.00.10240.16384      SQLSRV32.DDL SQL Server Native Ckient 10.0        2009.100.6000.34       SQLNCLI10.DDL


    Author: parcaya (parcaya@compuamerica.com.ve)
  4. parcaya said Sorry but did not work. Any ideas? Thanks for you attention

    Thanks for the info. But could be more specific about what exactly is not working? Did you try both ODBC drivers (SQLSRV32.DLL & SQLNCLI.DLL)? And what kind of error do you get when you try to store data in a “SMALLDATETIME” and “TIMESTAMP" field? I would expect something like this:

    22008 [Microsoft][SQL Server Native Client 10.0]Datetime field overflow. Fractional second precision exceeds the scale specified in the parameter binding.

    It might be a good idea to create a log file with (e.g.) $ioprint = 127. This should give us more details about your environment and the error. Hope this helps. Daniel


    Author: diseli (daniel.iseli@uniface.com)