Answer: Follow the normal process for installing SQL Anywhere 16 or 17; versions 16 and 17 of SQL Anywhere can coexist on the same computer as all other versions from 6 and up.

There is one caveat, however: The SQL Anywhere 16 and 17 installations modify the Windows PATH environment variable. If you have been relying on the PATH to determine where SQL Anywhere utilities such as dbbackup.exe and dbvalid.exe are located, your Windows command lines and batch files may start executing the version 16 copies of those utilities instead of the version you want. Either change the PATH variable, or modify your Windows command lines to explicitly specify the folder containing the utilities.

Each version of SQL Anywhere comes with its own environment variable that makes it easier to code commands; here's an example of how to use the SQLANY10 environment variable to execute the version 10 copy of dbvalid.exe:

   "%SQLANY10%\win32\dbvalid.exe" -c "ENG=ddd10;DBN=ddd10;UID=dba;PWD=sql" -d -o dbvalid_log_ddd10.txt

Here's a list of the environment variables for each version:

• Version 6: ASANY

• Version 7: ASANY7

• Version 8: ASANY8

• Version 9: ASANY9

• Version 10: SQLANY10

• Version 11: SQLANY11

• Version 12: SQLANY12

• Version 16: SQLANY16

• Version 17: SQLANY17

See also...
What are the Foxhound system requirements?