Obtaining the latest version of SQLSSC32.DLL will resolve this problem. Below is a detailed explanation of this problem for earlier versions of SQLSSC32.DLL.

As of Open Client Version . . , CT-Lib now uses a small datetime as it's default. (A small datetime keeps year, month, day, hour & minute). This means that the . . client will not even attempt to send second and millisecond data to the server when you post a record. The problem is that if the data was written with second and millisecond precision then we have no way of reselecting it using Open Client . . . (for example :30:23. doesn't equal :30:00.000) In versions eariler than this (for example . .0) CT-Lib used long datetime as it's default. (A long datetime keeps everything a small datetime does plus seconds and milliseconds). As a result when you upgrade your Sybase client you begin to see this problem.

One possible workaround is to change your Update Mode to be WhereKeyOnly or WhereChanged but if the datetime field is part of the key or you change the value of the datetime field you will still see this problem. You could also use small datetime fields when you are designing your tables and avoid this problem entirely. We are aware of this problem and we are looking in to possible solutions.

versions affected: Open Client .5, . . , . with ebf7398 applied, 0 with ebf7438. 3/26/99 0:44:29 AM