Bill's answer is more on the pro side of things. One "con" is that the client installer for Windows will give you all interfaces: ADO.NET, ODBC, OLE DB, etc. If you use the Deployment Wizard, you can choose the specific interfaces to deply, as opposed to getting them all.

Another con is that the client install for Windows includes the JRE used by the admin tools. You can build a much smaller package using the deployment wizard if you don't include the admin tools.

@Bill: That's an important disadvantage for simple client installs, say in a corporate install where Deployment Wizard setups often are just 3-4 MB small. - IMHO, the main advantage (besides the much broader platform support) is the inclusion of the menus. That's something I have missed in the Deployment Wizard:)

@Bill: Two further questions: 1. Is the created install a "SQL Anywhere standard installation" (i.e. with the original SA product code)? 2. Can it be EBF'ed afterwards? (If so, that were additional differences - and possibly advantages - compared to the Deployment Wizard.)

@Volker: 1. Yes, the install is just a subset of the SA standard installation, so has the benefit of being "guaranteed" to work. By guaranteed, I mean that it has the same bugs as the full SA installer :). 2. It can be EBF's afterwards, but not by the full SA installer. It has a different product code, so requires a separate installer. We haven't posted one yet, but we're working towards having EBFs for the client install as well. They will be smaller because they don't include the JRE.