More specifically, versions prior to 5.5.02 do not have the NEAREST_CENTURY
option. On versions without this option the engine will assume all 2 digit
years start with 19. Other than adding this option we made no changes for
Y2K complience.
All date functions have been Y2K complient since the beginning as we have
always stored 4 digit years
So you will be OK if your application ALWAYS provides 4 digit years when
accessing the database.
/steve
--
Stephen Rice
Manager Custom Support
Sybase Canada Inc.
email: sr...@sybase.com
Leo Tohill wrote in message <36713eff.6024
...@forums.sybase.com>...
>>Can anyone tell me, if the runtime version of Sybase SQL Anywhere 5.0.03
>>is year 2000 compliant? At the Sybase WEB site I found that SQL anywhere
>>5.5.02 is certified compliant, but it doesn't say anything about earlier
>>versions.
>5.5.02 is the earliest certified version. Earlier versions are not
certified.
>Leo Tohill - Team Powersoft
>-- Please post in newsgroup, not via email <