Hi all Is there any way to verify before executing whether a PROC SQL query may run fully in-database? ex: LIBNAME DB2 I'd like to reduce data movement/translation and leverage PROC SQL's use of the Pass-Through Facility but if the database itself cannot process the query than I'd like to avoid PROC SQL from processing any portion of the query itself. Also, is it possible to copy to the log PROC SQL's translated query destined for the pass-through facility? (i.e. describe w/o executing) This may help when translating SQL syntax across different DBMS. Thanks for your help in advance. ... View more

Hi all In SAS EG, when selecting a remote server as the Selected Sever, I understand any macros that were defined locally within that project (Selected Server Local) aren't copied/defined to the remote server. I am interested in copying/defining these macros on the remote server without having to copy the local SAS programs w/ embedded macros to the remote server. In SAS EG, I understand you’re able to attach a local external SAS program to the project and run that code on the server. However, if you have those embedded macros grouped by separate SAS programs, you may not use the %include statement to batch define them as they will try to reference the remote server location rather than the location of that local external SAS program. Any thoughts? Thanks for your help in advance. ... View more

Hi all I am interested in showing the inline descriptions for parameters used by my autocall macros. (i.e. To add a description for PARAM_NAME, add an inline comment after the parameter). I understand these descriptions aren't shown unless the macro has been compiled. Is there a way to compile all or some autocall macros stored as .sas files in an autocall folder without executing them or feeding them any parameter values? Example: autocallmacro.sas %macro autocallmacro(parameter /*First parameter*/); %mend; SASEG:      %autocallmacro( Autocall macro(Name) Name: First Name      I'm using the following code to: /*Enable the autocall library:*/      options mautosource mrecall sasautos = ("C:\AutocallLibrary\" sasautos); /*List all macros currently defined in work.sasmacr:*/ proc catalog catalog = work.sasmacr;      contents out = work.list; quit; /*Clear out all macros currently defined in the work.sasmacr (Note: Used for developing/debugging autocall macros):*/ proc catalog catolog = work.sasmcr et=macro kill force; run; Any thoughts? Thanks for your help in advance! ... View more

Hi all, I'm writing to ODS HTML output and I'm having some difficulties with using the ODS Report Writing Interface (Object-dot syntax). I am having difficulty using overrides to justify the text for all left/center/right within a cell, a column, column/cell span, and straight text. Regardless of overrides - Within a cell, the text is always centered. Outside a cell, left justified. I am having difficult in setting the sizes of cells, columns, and their associated gutters. (Using gridded_layout for HTML) I have had to use a blank column with ALT-255 hidden spaces to compensate. Any thoughts? All web references/papers for ODS Report Writing Interface/ODS Data Step Object seem to refer to ODS PDF. I've purchased the Output Delivery System: The Basics and Beyond. Only a checkmark and note that "Exciting changes are on the way for ODS and the DATA step... Refer to the SAS Web site for more information." Any possibility of some help for ODS HTML? Thanks for your help! ... View more