Is it safe to say connection parameter values cannot contain semicolons?

[Breck_Carter]

The Help topic Using connection parameters and connection strings seems to answer "Yes": a semicolon separates each connection parameter

I need to pick a character to delimit individual entries in a string of connection names used for another purpose.

[VolkerBarth]

Obviously, when masked, they can:

"%SQLANY12%\\Bin32\\dbisql" -c "DBN=demo;ENG=demo12;UID=DBA ;PWD=sql;CON='MyApp;App'"

creates an DBISQL connection named "MyApp;App". When using APP='MyApp;App' the behaviour is different: the semicolon and the following texts seems to be ignored, as APPINFO just returns "MyApp".

---

Well, no actual code, but real command lines:)

[MCMartin]

Should there be a backslash in the first statement?

[VolkerBarth]

Well, there are two backslashes in the path - otherwise, I would not know where to add one?

(I've just noticed that there's a blank behind the DBA - but that doesn't seem to do harm:)

[VolkerBarth]

Well, SQL Anywhere seems to treat the CON value with semicolon not consistent, as the following screenshot for DBSQL 12.0.1.3554 shows: