Can a System DSN be used to connect MessageStats Reports to the database?
Yes, the following steps can be used to configure MessageStats reports to use a System DSN to connect to the database; however, this procedure has not been officially tested by the Development and Quality Controls groups.
The form of the connection string would be:
Provider=MSDASQL.1;Persist Security Info=False;Data Source=NameOfTheDataSource
The connection string can be directly entered in the following registry key:
HKEY_LOCALMACHINE\SOFTWARE\Quest Software\MessageStats\ClientDB\SQLConnect
If anything more than default settings are required to connect to the DSN, then the following procedure is recommended:
1. Create an empty UDL file. Unfortunately there isn't a way to do this directly through the Windows User interface, so this can be done by opening Notepad and saving an empty file as a UNICODE file. To save the file as UNICODE, select Unicode in the Encoding list box at the bottom of the save dialog and select All Files in the Save as Type list box, then specify a filename that has an extension of .udl.
2. Configure the UDL file to connect to the data source by double-clicking on the saved file, and in the UDL configuration dialog, on the Provider tab, select Microsoft OLE DB Provider for ODBC Databases. On the Connection tab, select the Use data source name radio button, and specify the name of the data source, then click OK.
3. Configure MessageStats reports to use the UDL file created in step one by setting the following registry key: HKEY_LOCALMACHINE\SOFTWARE\Quest Software\MessageStats\ClientDB\SQLConnect to the following string: File name=FullPathNameOfTheUDLFile.
For example, File Name=C:\Program Files\Quest Software\MessageStats\SystemDSN.udl
