About terryeastman

terryeastman · ‎06-24-2025

MLE is an 'internal product' created within TD using SAS Studio as the base.

terryeastman · ‎06-24-2025

You're right. That wasn't the situation of my original post. It appears SAS procedures do not work the same as a LIBNAME statement when interacting with EXCEL. BOTH PROC EXPORT and PROC DBLOAD generate fake blanks regardless of the server environment - PC SAS, UNIX, SAS Studio. LIBNAME preserves a true null w/o turning it into a fake blank. I tested and confirmed this. Regretfully, we can not use a LIBNAME statement in SAS / MLE b/c the enduser insists on an XLS extension. MLE was designed such that PCFILES is not an option. Only XLSX extensions are possible with a LIBNAME statement in MLE. Confirmed with MLE support.

terryeastman · ‎06-23-2025

The core issue appears to be populating Excel with a LIBNAME statement vs PROC EXPORT. LIBNAME treats a NULL as a NULL. PROC EXPORT introduces a fake blank. Using a LIBNAME in MLE allows for only an XLSX extension (I'm waiting for MLE support to see is XLS is in any way available besides PROC EXPORT where it fails the test). Our downstream users insist on an XLS report. In a perfect world, in SAS Studio MLE, we would use LIBNAME rbretail pcfiles path=''&transformations_macro_var"; In our non SAS Studio code we have need using the following for over 15 yrs LIBNAME rbretail pcfiles path="&PATHOUT\rb_retail_B3R.xls"; They will not accept xlsx.

terryeastman · ‎06-19-2025

Thank you

terryeastman · ‎06-18-2025

Thank you. I started that too.

terryeastman · ‎06-18-2025

The issue stems from the downstream user of our output no longer able to use it (after 2 decades of non-issue) b/c SAS Studio / MLE either populates excel differently or, as an MLE support person suggested, there may be an issue when transferring the excel output out of MLE / SAS Studio

terryeastman · ‎06-18-2025

The actual data step has been in use for nearly 2 decades. The issue of the stored results in excel only started as we move to SAS Studio / MLE

terryeastman · ‎06-18-2025

This was a simple example of the true data step.

terryeastman · ‎06-17-2025

DATA TEST; do x=1 to 100; y=''; end; RUN; PROC EXPORT DATA=test DBMS=xls outfile="o:\SAS_file.xls"; RUN; The result should show column y as 100 null values in Excel using isblank excel function, the result is FALSE. It should be TRUE A comment from the MLE support team was ... Cursory examination says its possible that the SAS export or the change of environment (Linux Vs. Windows) means the cell is loading with an empty string instead of true empty until interacted with. However this is a question regarding SAS export behavior on Linux Vs Windows, and would better be put to SAS support. Trzaskos, Janel J We have a community hub with SAS for such questions, correct? Thank you Terry

terryeastman · ‎06-17-2025

PROC EXPORT to excel appears to insert a blank when the SAS value is null. You can test this by using the excel isblank function. Using PC SAS, a null value in the SAS dataset results in a null value in the excel. Using SAS Studio, it results in a blank in excel. Our down stream users of our report can not accept blanks ... only nulls

terryeastman · ‎06-17-2025

Using SAS Studio Datapool issue Detail: Create a SAS data sets with a few variables containing nulls. Export to excel download to local drive explore the nulls with =isblank(T2) result is FALSE click on cell T2 and then in the box displaying null value then click in any other cell. NOTE: did not touch the keyboard. ie did not change the value of cell T2 result changes to TRUE The result is always TRUE when running the same process not in SAS Studio. Question: What settings need to change in SAS Studio to make SAS / excel behave when using SAS / Excel outside SAS Studio ? PC SAS and SAS in DCJ environment pose no issue. The issue exists only in SAS Studio I did try three reruns of the code with each change 1. COMPRESS fnt 2. STRIP fnt 3. OPTIONS MISSING=''; All outputs had the same result of a 'fake' blank in the cell T2 NOTE: Using notdp

terryeastman · ‎03-24-2023

Same issue just starting to appear consistently in all our processes. I wonder if there was an update to SAS and / or Microsoft excel that creates the issue in the background. Our processes have been running w/o issue since extensions were XLS. XLSX worked too up until very recently

Online Status	Offline
Date Last Visited	‎07-03-2025 03:19 PM

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

Re: PROC Export to EXCEL preserves a fake space

PROC Export to EXCEL preserves a fake space

Re: CLI error - too many client tasks

SAS Inner Circle Panel