I mean I am sure we can implement a work around but understanding what has happened to have caused this would be helpful overall in case this becomes a new feature with other tables. ... View more

 ok, I get that something has changed but so far, all of my trouble shooting steps seem to point to the underlying table changing in some fashion to have caused this. Here are some of the log details... 8 proc sql; 9 connect to odbc(dsn=example ); 10 create table work.visit as select * from connection to odbc 11 12 (SELECT * FROM Tbl_Visit); ERROR: CLI cursor fetch error: [Microsoft][ODBC SQL Server Driver][SQL Server]Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. 13 disconnect from odbc; 14 quit; NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE SQL used (Total process time): real time 1.73 seconds cpu time 0.25 seconds   I also tried accessing the data set using a libname and data step and still receive the same error... 1 libname JSY odbc dsn="example" owner=dbo; NOTE: Libref JSY was successfully assigned as follows: Engine: ODBC Physical Name: example 1 ! run; NOTE: 7 table(s) not displayed/returned because the name is too long. 2 data visit; 3 set JSY.Tbl_visit; 4 run; ERROR: CLI cursor fetch error: [Microsoft][ODBC SQL Server Driver][SQL Server]Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. NOTE: The DATA step has been abnormally terminated. NOTE: The SAS System stopped processing this step because of errors. NOTE: There were 7269 observations read from the data set JSY.Tbl_visit. WARNING: The data set WORK.VISIT may be incomplete. When this step was stopped there were 7269 observations and 192 variables. NOTE: DATA statement used (Total process time): real time 1.83 seconds cpu time 0.28 seconds   The last time this ran correctly the observations were 10714 so there's that. The only way I can see the data is to view it interactively in SAS. I also had one of our SQL programmers use similar SQL code in that environment and he was able to read it in with no problems.  ... View more

Not sure what you mean by showing the whole code.  That is the whole code in my mind.  Again, this same code works with every other table in that database but this one and even then the same code worked up until a month ago. ... View more