Please right click on .chm file in your Windows Explorer and unblock it: find Unblock command in either context menu or in the Properties dialog.

This is a windows security feature that can be disabled to view the file. Click Here for an article on this.

ApexSQL applications will only store your SQL password if you enable the password saving option while creating a new project and connect to the server. If you choose to save the password, it will be saved in an encrypted format. Nobody will be able to use your credentials on another PC.

Use the ellipse button and add your server from the list of located servers to the existing servers list.

If your server is not shown in the located servers list you can type in your servers name directly to the server name field. It will be saved for future reference.

Go to the folder where you have installed the application to. There you will find a file named ApexSQL[Program name].com (for example, ApexSQLDoc.com). This is the console application you call in command line scripts. Note, that there is also a file named ApexSql[Program name].exe. Do not use this file in your scripts. This file starts the GUI and you’ll get an error when you try to run it from the Command Line.

Here are some examples of correct use

ApexSQLDoc.com /?
ApexSQLDoc /?

Incorrect use

ApexSQLDoc.exe /?

No. ApexSQL currently supports only Microsoft SQL Server (versions 7.0, 2000, 2005 and 2008).

ApexSQL applications offer support for the following SQL Server versions: SQL Server 7.0, SQL Server 2000, SQL Server 2005 and SQL Server 2008.

Click Help -> Check for Updates menu item.

This will display auto-updater dialog and check if a fresher version is available on our site. If there is a new application version you will be prompted to download the necessary updates.

Mark Automatically check for updates on application start-up option of the auto-updater dialog if you want to check for updates on each application start-up.

Click Help -> Check for Updates menu item, then click Options and uncheck Automatically check for updates on application start-up option. Click Here for a Knowledgebase article on this.

For a list of all system requirements and pre-requisites please see System Requirements.

In most cases yes, please see System Requirements for an updated list of supported systems by product.

First way is to set up an alias for your server using SQL Server Configuration Tools and then use this alias with our products.

In case of SQL Server 2000 please use Client Network Utility tool :
Start | Programs | Microsoft SQL Server

in case of SQL Server 2005 or SQL Server 2008 please use SQL Server Configuration Manager tool:

MS SQL Server 2005: Start | Programs | Microsoft SQL Server 2005 | Configuration Tools
MS SQL Server 2008: Start | Programs | Microsoft SQL Server 2008 | Configuration Tools.

Find their Aliases tab or treeview node and add the alias pointing to your server name and a port value.

Second way is to point your server in our products in the following manner:
TCP:Server_name,port_number
So, if your server is PC\SQL2008 and port is 1500, the server name string will be as following:
TCP:PC\SQL2008,1500

Some do. These are ApexSQL Edit, ApexSQL Diff, and ApexSQL Script. In ApexSQL Edit, it allows you to connect to and work with supported version control systems directly from the application without requiring any additional version control client software. In ApexSQL Diff, it can be used to compare and synch various data sources with scripts stored in source control. In ApexSQL Script, it allows you to script directly to source control. These products integrate with Microsoft Visual SourceSafe 6 or Microsoft Visual SourceSafe 2005, Subversion 1.6.x and below, SourceGear Vault 3.5, 4.0.x, 4.1 and 5.0 Microsoft Team Foundation Server 2005, and Microsoft Team Foundation Server 2008 (SP1).

Subversion
1.6
1.5
1.4
Team Foundation Server
2008
2005
SourceGear Vault
5.0
4.1
4.0
3.5
Visual Source Safe
2005
6

These products also integrate with other MSSCCI-compatible source control systems not mentioned above.

There is no need for additional software installations. All products provide a direct and "native" client interaction with a Source Control system.

Yes. There are no limitations to what you can connect to – be it a shared Source Control server in a network workgroup, a domain or on the Internet, or a local Source Control database used for single user project development code versioning.

Yes. If the Source Control system in question supports secure connections, such as Subversion, SourceGear Vault or Team Foundation Server through HTTPS protocol, the products will work seamlessly when the "https://" URL is specified and the connection to the Source Control system server will be secured. This means all the data retrieved from and sent to the Source Control system will be encrypted over the network.