Hello all...we have successfully migrated our Sybase ASA
9.0.2 DB to SQLAnywhere 11.0.2044 DB. Previously, to connect
our front-end apps to the database, we used the SQL Anywhere
11 driver in our ODBC settings which led to some unexpected
behavior, for instance we had to put our SELECT statements
in double quotes if a column in the SQLAnywhere table was a
reserved word in SQLAnywhere. Instead of using the SQL
Anywhere 11 driver, we tried the old one called Adaptive
Server Anywhere 9.0. This seems to work quite well. The
question I have is: are there any disadvantages to using the
Adaptive Server Anywhere 9 driver with a SQLAnywhere
11.01.2044 DB? I understand that this is a very general
question and I was wondering if anybody out there has tried
this.

There will usually be that level of backward compatability
support in our product ... but given the 9.0.2 will be
going past it End of Life at the end of January the
lack of future engineering fixes for that makes a strong
case for addressing the main question.

The need to quote reserved words is nothing new though.
So I am a little confused why this is an issue or why you
think the client version would make a difference here.

It does sound like a known bug that is fixed in the currently
available ebfs:

================(Build #2117 - Engineering Case #551146)================

When creating or renaming an object, if the name specified was a SQL
keyword,
Sybase Central could have erroneous issued a warning that the specified
name
would need to be double-quoted when used in a SQL script. This has been
fixed.
Now, Sybase Central only issues a warning if the specified name is both a
SQL keyword and a SQL reserved word.



<Mark> wrote

Thanks Nick...