|
Syteview uses ODBC Data Sources to talk to your Microsoft SQL Server. The DataGrabber programs and the ASP2SQL.DLL Data Control each use an ODBC Data Source. The DataGrabber programs are usually run on the computer hosting your SQL Server, and the Data Control is always run on the computer hosting your Microsoft IIS Web Server. If you are hosting both of these on the same computer then you will only have to create the SQL Server ODBC connection one time, otherwise you will need to create an ODBC connection on each of the computers. In either case the process the same. To create an ODBC Data Sources go to the Control Panel and open the Administrative Tools folder. From the Administrative Tools folder open the Data Sources (ODBC) applet. Switch to the System DSN tab and click the Add button 
On the next screen highlight the SQL Server driver and click the Finish button. 
On the next screen fill in the Data Source Name, Description and the Name of your MS-SQL Server. The Name must be SQL-Server. Description can be anything you choose. You must put the name of your MS-SQL Server in the Server field. Then click the Next button. 
On the next screen make sure you select Windows NT authentication using the network login ID. You may choose to checkmark the Connect to SQL Server to obtain default settings for the Additional configuration options, but it is not required by Syteview. Now click the Next button. 
On this screen change the Default Database to Syteview®. Also checkmark the Use ANSI quoted identifiers and the Use ANSI nulls, paddings and warnings. Click the Next button. 
The settings on the next screen are not essential to Syteview. Accept the default settings or change them for your particular application. Now click the Finish button. 
The next screen shows the settings of the ODBC Driver you have just created. Click the Test Data Source button. 
Hopefully you will see the following screen and you will have successfully created the ODBC Driver that will connect to and retrieve data from your Microsoft SQL Server. If not, make sure you are creating the driver on your SQL Server and try it again. 
|