SAS Support Communities

SAS_Ryan · ‎08-14-2018

Is there a way to programmatically loop thru all variables in a dataset and convert any date variables into character variables? I need to push my data to a 3rd party visualization software and it does not like the SAS formatted dates. This code does the conversion I need, can it be macrotized to automatically convert for every date variable? data my_dataset; set my_dataset; if my_date ne . then my_date_ch = put(my_date, mmddyy10.); else my_date_ch = ''; run;

SAS_Ryan · ‎09-28-2017

My coding style is to explicity define inner/left joins. That said, I've increasingly run into code like this which is effectively an inner join: Proc SQL; Create table abc as select * from table1 A, table2 B where a.key = b.key and a.id = b.id; quit; I recently ran into this: Proc SQL; Create table abc as select * from table1 A, table2 B where a.key = b.key (+) and a.id = b.id; quit; Can someone tell me what the (+) is doing?

SAS_Ryan · ‎08-03-2017

Data is on a SAS SPD server. Which being a SAS product, I thought stored data as sas7bdat files. I guess I thought wrong!! Removing the row limit for ACCESS datasets does fix the problem.

SAS_Ryan · ‎08-03-2017

I'm looking to see the number of records in a table, and am frustrated by EG's behavior when a table exceeds row limits. Under table Properties -> Advanced I see 10,000 rows as the record count. This is in fact the row limit, not the number of records in the table, because if I run: Proc sql; select count(*) from table; quit; I get the actual number of rows. Of course I can run proc sql for every table, but thats a pain. In Base SAS table properties would give you the actual row count. Am I missing something in EG? Why is this so inconvenient?

SAS_Ryan · ‎07-18-2017

Maybe I'll somewhat answer my own question here: When running Base SAS at my previous job, exporting .csv files to a Windows folder location was no issue because well SAS was on Windows. Using EG, with the SAS server on UNIX, I'm unable to post to the Windows folder because the SAS code is getting executed in UNIX, not locally. Ultimately the .csv files are going into Excel reports, so as a workaround instead of importing .csv files I can just use the SAS addin for Excel to connect directly to the .sas7bdat files in UNIX, and skip the .csv files entirely. I'm sure there are many ways to do it, but this might work. Still learning to think in EG instead of Base...

SAS_Ryan · ‎07-18-2017

I'm fairly new to EG, but experienced as a Base programmer. I've got a bunch of SAS Projects I'd like to convert to SAS Programs. When I click "Export All Code in Project," I'm able to generate code from the project, but I'm finding items missing from the process flow, such as an export step from a SAS table to .csv file. So two questions: 1. Am I just not doing the conversion to code correctly? Or are there inherently some process flow steps that won't convert to program code? 2. If some process flow steps simply don't convert to code, what other type items should I watch out for beyond the .csv export steps? It seems crazy to me that .csv exports wouldn't convert to code. They're easy enough to write in code, and I can, I'd just prefer to use automation if possible. Using SAS EG 7.13HF3

Online Status	Offline
Date Last Visited	‎08-15-2018 06:52 PM

SAS Support Communities

Macro to loop thru all date variables and convert to character type

SAS SQL "joinless" syntax

Re: How to see record count in a table where row limit has been reache...

How to see record count in a table where row limit has been reached

Re: Export All Code in Project - Missing some Program Flow items?

Export All Code in Project - Missing some Program Flow items?