Thanks for your response. That explains why the SAConnection.Open() sets the CHAINED option to ON after opening the database connection. As I am connecting to the utility database (utility_db), which I do not think supports executing the CHAINED statement (see http://dcx.sap.com/index.html#sqla170/en/html/815404366ce21014b496ac686acbb35b.html), my application throws an exception on connection. Does SQL Anywhere 17 support connecting to the utility database via the .net SAConnection?
Thanks