Latest release - version 16.0

[AnnePetteroe]

Hello,

In the latest release we are noticing that before we did the upgrade the date format was in Date/Time and now it is in short text which is causing issues with our Microsoft Access file.

Has anyone else experienced this or know how to fix it?

Thanks!

[AnnePetteroe]

Hello Maureen,

Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend that you familiarize yourself with https://community.sap.com/resources/questions-and-answers, as it provides tips for preparing questions that draw responses from our members.

Feel free to take our Q&A tutorial at https://developers.sap.com/tutorials/community-qa.html as well, as that will also help you when preparing questions for the community.

By adding a picture to your profile you encourage your readers to respond.

Kind regards,
Anne

[sladebe]

Is this for the ASE product? How "latest" is latest? Can you give an example? I'm not seeing any difference in 16.0 SP04 PL04

[Mark_A_Parsons]

Need more details ....

• ASE version (select @@version)
• reproduction example (eg, small table, sample insert, before/after results of select that's of issue)
• confirmation that your code is not changing dateformat or language? (set dateformat / set language)
• does this issue arise if you use the command line tool 'isql' to run your select? (need to separate dataserver from client/app/driver)

[maureensiwiec]

Hi Ben,

16.0 SP04 from March 2023

[ChrisBaker · Accepted solution]

That is a very old driver. ASE, SRS, OCS and SDK (containing the current driver) are released together with the same release and patch level (since ASE 16.0 SP03GA. You should install the newest available driver.

The ODBC driver does not use the sql.ini file by default. It is a direct protocol driver. If changing to a newer driver does not solve the issue, you will have to locate the documentation in Microsoft. I find several references to how to work around 'date' datatype columns coming in as text instead of a date format.

Chris

[maureensiwiec · Accepted solution]

Thank you everyone for your help! And thank you Chris, I updated the ODBC driver to the latest version and that resolved it!

Thank you!

[ChrisBaker]

I agree with Ben. ASE 16.0 was introduced in 2014. The most recent version is ASE 16.0 SP04PL04 released this year. No date/time storage changes have been done then or recently.

Please check your ODBC driver and Access settings. I remember that for ODBC and Access, there is a setting (flag?) or ODBC configuration that needs to be added to the .ini file or Access data source to ensure dates are passed as dates, not strings. This is nothing to do with ASE or our ODBC driver but how the data from ODBC is used by Access.

I would assume that as part of your upgrade, you may have had to re-create the DSN for the newer ODBC driver. Old settings would not have applied to a net new DSN/driver.

Chris

[maureensiwiec]

Thank you Chris!

I confirmed it is 16.0 SP04 PL04 30648 on a windows 2012 R2 64-bit

I will check your other suggestions

[maureensiwiec]

Hello,

We are on 15.07.00.1300 SYBDRVODB64.DLL - is there a new ASE driver that would be for SAP version 16 and if so where can I download the newest or at least base version 16 driver?

For the part of the flag to be added or ODBC configuration to the .ini file, just to confirm that this is the C:\sybase\ini\sql.ini file? This was checked but we do not see any flags.

Also with our setup the .ini file where Access is used is on a different machine than the DB server.