That only suppresses the warning message. It doesn't solve the problem that resulted in the warning message. ... View more

Just a thought - have you checked into the possibility that the error message needs to be taken literally? i.e. Is there a problem with the disk itself? I would have thought drive problems would result in error messages from Windows itself, but one never knows. ... View more

Just an observation - If you select Export from the file menu, one of the options is to have SAS write out the SAS code that it generated. You can then append it back into your program and continue writing your program from there. I usually do that when I need code in a SAS program to import or output; it means I at least have a starting point for getting the syntax right. ... View more

Are you perhaps trying to escape the quote using an exclamation mark? i.e. are you trying to get the two character sequences '7 and '8 as members of that list? If that is the case you can't do it that way in SAS. If for some weird reason that I don't understand you are unable to use double quotes in your code, you can also use two consecutive single quotes as a literal single quote. e.g. x='''7'; assigns the two characters '7 to x. If you actually want the exclamation mark in there, then x='!''7'; assigns the three characters !'7 to x. ... View more

if x=1 then x=2; if y=9 then y=.; ... View more

Also take a look at http://support.sas.com/resources/sysreq/hosts/pc/ regarding supported OS's. ... View more

He might be OK regarding precision issues depending on the hardware he is running on. I count 15 significant digits in all his numbers. According to http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/viewer.htm#numvar.htm with 8 byte numerics Windows does support 15 significant digits. ... View more

If you are using SAS interactively, look at OPTIONS DMSSYNCHK. Be warned that SAS broke that a little bit in 9.2 as compared to 9.1.3. I don't know if they repaired it in 9.3. In 9.1.3 if you hit an error with DMSSYNCHK on it would stop subesquent steps that had already been submitted from running but would still allow you to resubmit without problems. In 9.2 if you hit an error with DMSSYNCHK you seem to have to restart SAS to get out of that error state. Still, even if you are stuck in that state you can still look at your datasets, logs, etc. ... View more

Interesting! I had a vague understanding that you could make SASUSER read-only (but had never tried), but didn't realize that would let you share the profile between multiple sessions. I normally just use one session at a time and swear under my breath when I absent-mindedly open a second session and it complains. Thanks! ... View more

Oh, really? Even in SAS 9.1, macro variables inside single quotes aren't supposed to be resolved. Are you sure you are remembering correctly? ... View more

I had similar problems a few years ago when I was having SAS "talk to" Access a lot. In addition to options validvarname=any that Ksharp mentioned, you will probably need to use name literals (I think that's what their official name is), e.g. "1Quarter"n (note the n following the quote to indicate it is a name, not a string). Try something like options validvarname=any; data new;      set old;      rename "1Quarter"n = Quarter1; run; ... View more

One problem with making SASUSER read-only is that that is where your SAS profile lives. If SASUSER is read-only then SAS can't save your preferences from session to session. It is occasionally useful to make one of your own SAS libraries read-only temporarily, to avoid lost data from coding mistakes. e.g. libname test "C:\test" readonly; If you do that then SAS will not permit you to make any changes to the datasets in that library while that libname statement is in effect. ... View more