You need to be more specific about what you mean by "suppress".  If you mean you want to remove a column from part of a SAS dataset (while leaving it in for other months where values are not null) then the answer is that you cannot.  The table structure applies to all rows in the table. Richard ... View more

An in-line view can be reused. Is there a difference in the way a query is executed using either an in-line view or a subquery?  Possibly, but this would be up to the query optimiser to determine.  Is there a difference in the way a query is developed using either an in-line view or a subquery? For a complex query it may be easier to design and test one or more in-line queries independent of the main query.  There may also be benefits for code maintenance. Richard ... View more

Have you tried loading the SAS Add-In for Microsoft Office?  That would allow you to "see" the data in a SAS table as columns in an Excel spreadsheet, and you could define your pivot table over these columns. Richard ... View more

If you still have difficulty with the upload process you might consider creating a format control file (here, for the LIBRARY library) in the current environment Proc format library= LIBRARY cntlout = work.formatlib ; run Then upload the SAS dataset created, just like any other SAS dataset In the remote environment Rsubmit ; Proc format library= LIBRARY cntlin = work.formatlib ; run Richard ... View more

I was faced with a similar requirement in student enrolment data, where hundreds of exceptions had to be monitored and the list of exceptions potentially could be enlarged from year to year.  I found it best to break the problem down into more manageable chunks, using SQL or datastep code as best fitted the type of exceptions.  Examples: 1. Null data in a field.  A data _null_ step (or a macro) could be used to generate from a list multiple statements of the type      If missing(abc) then do ; Exceptioncode = 'xyz' ; output ; end ;     A following datastep could then screen for all null exceptions.  Not suitable for conditions involving multiple nulls. 2. Generic range errors - check for non client specific out of range exceptions using formats created from the exception specifications - useful for identifying values above a maximum, or zero, or negative, or not in a list of specific values.  A data _Null_ step could create a dynamic list of exceptions of the type      Exceptioncode = Put(abc, xyz.) ; if not missing (Exceptioncode) then output ; 3. More complex conditions - if you have a relatively small number of clients with a relatively large list of specific exceptions it may pay to separate them out using       Where client = 'abc' ; 4. Otherwise create the if statements for complex conditions in another data _null_ statement. I quite like the idea of generating the multiple If statements in an external file and then using %include to process them.  It creates persistent, viewable and auditable lists of conditions that have been applied. Data Exceptions ;      Set rdbms.customer_info ;      %Include "Null_exceptions.txt" ;      %Include "Range_exceptions.txt" ;      %Include "Complex_exceptions.txt" ;      Keep id, exceptioncode, .... ; Run; Data ABC_Exceptions ;      Set rdbms.customer_info (where = (client = 'ABC')) ;      %Include "ABC_exceptions.txt" ;      Keep id, exceptioncode, .... ; Run ; Proc Append Base = Exceptions                     Data = ABC_Exceptions                     ; Run ; Richard. ... View more

Sophie Databases like SAS do not use cell references like spreadsheets.  Each column is treated as a variable, and the formulas work on variables rather than individual cells.  Thus the SAS formula equivalent to your example is      B = A + 1 ; (the same for every row) and it would be part of SAS datastep following your import from Excel. If you were to import the formulas as text, as suggested by @RW9 , all you would have is a column containing the text of the Excel formulas.  These values would have no computational significance in SAS and cannot readily be used to calculate resulting values from them. Now I am supposing that your real world example contains much more complex formulas than the simple example you have shown, and you may want to replicate such a formula in SAS.  If that is the case you may, with perhaps some difficulty, be able to convert an Excel formula into an equivalent SAS formula.  If you care to post an example closer to your real world formula that you want to "import" and we may be able to suggest the equivalent SAS code.  Any Excel functions in your formula will need to be replaced with SAS equivalents or code to provide the same outturn. Richard Message was edited by: Richard Carson ... View more