Correct!   I was looking for the same and found it.   Thanks.   - Dr. Abhijeet Safai ... View more

I just had similar errors, involved with ODS Excel, Proc Print, and a large dataset.  It turned out to be a picture format that once eliminated from the code stopped the errors.  To whomever it may concern in the future.   ... View more

I'm getting the same message now. Did you ever get this fixed? ... View more

I had the same issue then realized someone else had changed the name of the path directory where I was trying to place the EXCEL files. Make sure you have access to write wherever SAS is trying to write. ... View more

I am facing the same problem Have you sought out the solution of this problem??? If yes kindly guide me ... View more

@Kastchei Thanks for all the testing and debugging. As you already figured out: o  compile once I   case insensitive   As I understand it the o wouldn't be necessary when using a constant string. It's only of importance if you pass in the RegEx via a variable.   RegEx are resource intensive and though "slow". But they are really powerful when it comes to pattern matching.   As for the \w: Good catch!    Here some docu links. Especially the 2nd one (metacharacters) is sometimes a bit hard to find. http://documentation.sas.com/?docsetId=lefunctionsref&docsetTarget=n0r8h2fa8djqf1n1cnenrvm573br.htm&docsetVersion=9.4&locale=en  http://support.sas.com/documentation/cdl/en/lefunctionsref/63354/HTML/default/viewer.htm#p0s9ilagexmjl8n1u7e1t1jfnzlk.htm    Cheers, Patrick ... View more

if the magnitude is different, is there any format to add the decimals to integers? ... View more

Nevermind about my problem! I restarted SAS and just ran my data file and the code below and it worked. All i needed to do was change the file name.   proc template; edit Base.Corr.StackedMatrix; column (RowName RowLabel) (Matrix) * (Matrix2); edit matrix; cellstyle _val_ = -1.00 as {backgroundcolor=CXEEEEEE}, _val_ <= -0.75 as {backgroundcolor=red}, _val_ <= -0.50 as {backgroundcolor=blue}, _val_ <= -0.25 as {backgroundcolor=cyan}, _val_ <= 0.25 as {backgroundcolor=white}, _val_ <= 0.50 as {backgroundcolor=cyan}, _val_ <= 0.75 as {backgroundcolor=blue}, _val_ < 1.00 as {backgroundcolor=red}, _val_ = 1.00 as {backgroundcolor=CXEEEEEE}; end; end; run; ods html body='corr.html' style=statistical; ods listing close; proc corr data=ifsns noprob; ods select PearsonCorr; run; ods listing; ods html close; proc template; delete Base.Corr.StackedMatrix; run; ... View more

Hi: These comments fit my issues - Thanks again Cynthia!!! ... View more

See also: http://support.sas.com/kb/31/184.html ... View more

Arsenio- Did you ever get this figured out?  I want to do the same thing. Thanks, Melanie ... View more

Hi Tim,   Thank you so much for it! I am kind of all-with-sas-code now, actually there is easier way without having sas coding involved. ... View more

 @kmw The page also states: Although these values appear to be alike, the internal representations differ slightly, because the IEEE floating-point representation can only represent 15 digits. This issue pertains to floating-point representation on the x64 processors.   I find these 2 statements misleading:   1- The 15 digit representation limit does not explain (the word "because" is used) in any way that SAS reads these numbers in this way: 3FE0000000000000 L=21 NB=0.50000000000000000000000 3FE0000000000000 L=22 NB=0.500000000000000000000000 3FDFFFFFFFFFFFFE L=23 NB=0.5000000000000000000000000 3FDFFFFFFFFFFFFE L=24 NB=0.50000000000000000000000000 3FDFFFFFFFFFFFFF L=25 NB=0.500000000000000000000000000 3FE0000000000000 L=26 NB=0.5000000000000000000000000000 3FE0000000000000 L=27 NB=0.50000000000000000000000000000 3FDFFFFFFFFFFFFF L=28 NB=0.500000000000000000000000000000 3FDFFFFFFFFFFFFF L=29 NB=0.5000000000000000000000000000000 3FE0000000000000 L=30 NB=0.50000000000000000000000000000000 3FE0000000000000 L=31 NB=0.500000000000000000000000000000000 3FE0000000000000 L=32 NB=0.5000000000000000000000000000000000     2- Likewise, the floating-point representation on the x64 processors does not exhibit issues explaining this behaviour of only SAS only under Windows.   3-Unrelated to this discussion but related to numerical precision, and much much wider and very puzzling: The whole numerical precision issue exists because rational numbers were introduced to represent floating-point numbers.This seems like a ludicrous idea. Rational numbers were introduced to represent the mantissa value when negative exponents were used as part of the algorithm detailed above. Had the mantissa portion of the number kept positive exponent representations only, with the position of the decimal dot shifted using the exponent portion of the number, this numerical precision issue would not even exist. There must have been a reason to decide using negative exponents and try to represent the decimal portion of numbers using the sum of rational numbers. Do you know what on earth could this justification could be?     ... View more