Hi Cynthia,   There are a lot of things to learn with SAS.  We’re interested in learning DS2 and the integration of database access through FedSQL and program logic.  The use of SQL Server data would make these programs more realistic and even allow some performance benchmarking between different techniques.   The references to SAS/ACCESS for ODBC not being part of SAS University or listing engines that are part of other SAS/ACCESS products that are not part of SAS University is an unhelpful red herring.  My question and the code used to illustrate it only use SAS/ACCESS for PC Files and the pcfiles engine that is included with University Edition.   ***SOLUTION***  I have figured out the solution to my problem and am now able to read a SQL Server database table into my program in SAS University.  I had to stop the PC Files Server service running on the PC where I had installed the SAS PC Files Server and restart it as a desktop application.  The CLI error stopped occurring in University Edition and I could read a database table in a SAS proc or datastep using the libname created in University Edition.   I think that the fact that the SAS PC Files Server generates an error when running as a service is a bug that should be fixed.  This would be a good situation to document as a SAS Note in the Knowledge Base.   Paul ... View more