README.TXT The UDL samples included in this download are working samples that have not been modified (except for authentication). Some assumptions: FOLDER: C:\data\ FILENAME: northwind LANSERVER: LT3 REMOTESERVER: inters.com PASSWORD: password Edit these to match your names and authentication. User names are set to default admin names (postgres, root=MySQL, SYSTEM=Oracle, sa=SQL Server, dba=Windows Azure SQL Database). SQL Server providers examples include SQLOLEDB.1, SQLNCLI10.1, SQLNCLI11.1. Set your value to match latest driver (Azure can use SQLOLEDB.1, but test fails in the Data Link dialog box). Remove Integrated Security=SSPI if using server authentication. northwin.dbf is intentionally missing the d to comply with 8.3 naming data files are named northwind for consistency only. Except for Access files they do not contain the famous fictitious company's sales data. -- OPENING UDL FILES To edit and test the files you can use OLEDB CORE SERVICES, which is the Windows Explorer (File Manager) default. You can drag-and-drop UDL files onto the SQL OFFLINE application window file to open them. You can also open them with SQL OFFLINE from the Data ribbon File > Data Link (UDL). Source > UDL Save to save. You can create new UDL and data files from the Data ribbon File > New File. -- UDL32.BAT This BAT file is provided to help you run32-bit OLEDB CORE SERVICES and work around long-filename problem You can drag-and-drop UDL files onto the BAT file to open them. Doing this avoids a Microsoft Data Link Error: Test connection failed because of an error in initializing provider. [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. -- ONLINE HELP and VIDEO link http://inters.com/docs/udl.htm --end