The SAS Studio autocomplete function might not add data sources to your program code using the correct letter casing. This problem can occur when you are connecting to a case-sensitive database.
For example, suppose that you are creating a library with the OLEDB engine. The database that you are connecting to is configured to be case sensitive. In this case, the names of data sources in the library use both lowercase and uppercase letters.

Now, suppose that you need to sort a data source named THISisCLASSdatasource, which contains some characters in uppercase and others in lowercase. In new program code, you add the SORT procedure. If you use the autocomplete function when entering the SORT procedure, then a pop-up window displays all available data sources in the library, as shown in the following display. As you can see, lowercase and uppercase letters are displayed correctly in the window.

However, if you use the arrow keys to select and add THISisCLASSdatasource to the program code, then the data source name is added in lowercase letters, as shown in the following display:

As a result, when executing the program code, the following error is returned:
69 proc sort data=y.thisisclassdatasource; run;
ERROR: File Y.thisisclassdatasource.DATA does not exist.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE SORT used (Total process time):
real time 0.08 seconds
cpu time 0.00 seconds
To avoid this issue, do not use the arrow keys to select the data source name in the autocomplete window. Instead, enter the first character of the data source in the correct case (uppercase "T" in this example). The data source name is then added to the code with the correct letter casing, as shown in the following display:

Operating System and Release Information
| SAS System | SAS Studio | Microsoft® Windows® for x64 | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows 8 Enterprise 32-bit | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows 8 Enterprise x64 | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows 8 Pro 32-bit | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows 8 Pro x64 | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows 8.1 Enterprise 32-bit | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows 8.1 Enterprise x64 | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows 8.1 Pro 32-bit | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows 8.1 Pro x64 | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows 10 | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows Server 2012 Datacenter | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows Server 2012 R2 Datacenter | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows Server 2012 R2 Std | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows Server 2012 Std | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows Server 2016 | 3.8 | | 9.4 TS1M6 | |
| Microsoft Windows Server 2019 | 3.8 | | 9.4 TS1M6 | |
| Windows 7 Enterprise 32 bit | 3.8 | | 9.4 TS1M6 | |
| Windows 7 Enterprise x64 | 3.8 | | 9.4 TS1M6 | |
| Windows 7 Home Premium 32 bit | 3.8 | | 9.4 TS1M6 | |
| Windows 7 Home Premium x64 | 3.8 | | 9.4 TS1M6 | |
| Windows 7 Professional 32 bit | 3.8 | | 9.4 TS1M6 | |
| Windows 7 Professional x64 | 3.8 | | 9.4 TS1M6 | |
| Windows 7 Ultimate 32 bit | 3.8 | | 9.4 TS1M6 | |
| Windows 7 Ultimate x64 | 3.8 | | 9.4 TS1M6 | |
| 64-bit Enabled AIX | 3.8 | | 9.4 TS1M6 | |
| 64-bit Enabled Solaris | 3.8 | | 9.4 TS1M6 | |
| HP-UX IPF | 3.8 | | 9.4 TS1M6 | |
| Linux for x64 | 3.8 | | 9.4 TS1M6 | |
| Solaris for x64 | 3.8 | | 9.4 TS1M6 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.