I have a very similar problem. We used to have desktop licenses for SAS/PC, and recently moved to a server solution (also PC). And its giving us endless grief. Desktop setups are just so much simpler to work with. We can't import/export files to/from network drives, even with the network drives mapped. After a while we figured out that we can import, if you use the import step in EG, but not have any code accociated with it. Similarly we can export excel files to the network, but we can't export SAS data files (.sas7bdat) files to the network wit this method. It keeps on giving the error "Unable to export to xxxxxx.sas7bdat. Please ensure the target file is not already open within your project. If so, please close the file and try again."   I'd appreciate it if anyone has any insights...   ... View more

I believe that you can fix this problem with the following steps: (1) use SERROR, *not* NOSERROR, as the latter only maskes problems you may have; besides, if everything works as it should, you will not get a message - the presence of a message just tells you that you are doing something wrong   (2) instead of %let filenm = '/operations/FRAG/AQD&test.csv'; use %let filenm = %NRSTR(/operations/FRAG/AQD&test.csv); /* NRSTR "escapes" almost everything - see the manual for exceptions */   (3) instead of   proc import datafile=&filenm out=initial_list dbms=csv replace; use:   proc import datafile=%NRBQUOTE(&filenm) /* %NRBQUOTE escapes the expansion of &filenm here */ out=initial_list dbms=csv replace;   ... View more

Hi: You'll find papers written by developers here: http://support.sas.com/rnd/base/early-access/index.html and there's a bit on ODS LAYOUT in this paper: http://www2.sas.com/proceedings/sugi31/092-31.pdf If you search for user-group papers on the topic, you should find a few more. cynthia ... View more

Bill, You are right, if you don't ask, you don't get. Found a much easier solution actually. Our sharepoint allows (some users) to save as an Access 2007-10 DB with a linked table to sharepoint. Solves the problem! ... View more

The "cleansing" process is not part of a SAS program, but happens within EG processing on the client side of things. It works this way because if it tried to transfer the text file to the server for processing first, it's already too late. A text file whose encoding doesn't match the server's session encoding could already cause errors. If you text file is already on the server and you want to "clean" it, you would have to write a DATA step to read in the text content and emit lines that don't contain the offending characters. Chris ... View more

In case anyone wanders in here in the future, the solution is simply don't select a default. ... View more

I collected the encoded pw using PROC PWENCODE but hoped to hide my password from the stored log by using the NOSOURCE option. "Lazy" is not clever in SAS programming.[pre] option nosource ; proc pwencode in='my password' ; run; option source ; [/pre] still revealed the procedure syntax. It seems like the NOSOURCE option only takes affect after the line in which it is found, and not immediately after its statement. Here is a log snippet showing the effect of puting all the code on one line like the above [pre] 454 option nosource ; 454! proc pwencode in='my password' ; run; {sas001}bXkgcGFzc3dvcmQ= NOTE: PROCEDURE PWENCODE used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 454! o 454! ption source ; [/pre] When the option NOSOURCE is on a separate line, the syntax of the following lines are not displayed (until the line with option SOURCE). I won't make that mistake again 😉 PeterC ... View more

I don't know what the whitespace=nowrap is. At the beginning of each record I show with Proc Print, these are the respective HTML source codes: Undesired: Desired that I can't reliably replicate: ... View more

Hi: You might consider contacting Tech Support for help with this. The only similar thing that I've had happen is an SP that worked in EG, but failed in other client applications because I happened to use a JavaScript keyword as a parameter name, as described here: http://support.sas.com/kb/18/502.html Tech Support is in the best position to look at your actual SP code and help you figure out what is going wrong. cynthia ... View more

Hi...if you use a code node in EG, you can "sort" of generate the separate PDF files. There's an upside and a downside. The upside is that if you use NEWFILE=BYGROUP, the files get created automatically. The downside is that you can only "sort of" control the name of the file. For example, with the attached code: [pre] proc sort data=sashelp.prdsale out=prdsale; by division prodtype; run; options orientation=landscape topmargin=1in bottommargin=1in rightmargin=1in leftmargin=1in nodate number pageno=1; run; ods pdf file="c:\temp\GRFBY1.pdf" newfile=bygroup; GOPTIONS reset=all device=actximg; PROC GCHART DATA=prdsale; title 'The Graph Title'; VBAR3D region / SUMVAR=actual GROUP=product SHAPE=BLOCK FRAME TYPE=SUM PATTERNID=MIDPOINT; BY division prodtype; format actual dollar12.2; RUN; QUIT; ods _all_ close; title; footnote; ods listing; [/pre] If the SAS dataset has 4 BY groups, then the PDF output files will be named: GRFBY1.PDF, GRFBY2.PDF, GRFBY3.PDF, GRFBY4.PDF -- which means you can control the "beginning" part of the name, but NEWFILE= option wants to number the output files by incrementing the right-most number in the starting file name by 1 for each BYGROUP (in this example). Of course, after the files were created in c:\temp, you could go and issue a RENAME to name them what you wanted. Your only other alternative would be to "macroize" the program to produce a single BY group -- and then you can control the name of every BY group's file -- when you invoke the macro program for each group. And then you could call the files Tom.PDF, Rob.PDF and Jan.PDF. (or whatever else you wanted). Good luck! cynthia ... View more

Try to use automatic macrovariable &_METAUSER or &_METAPERSON. ... View more

Sorry, I only have EG4 to test with. When I do a Scatter Plot in EG4 and select the click path: Graph --> Scatter Plot and then after selecting Task Roles for my data (to put my date on the horizontal axis), I can select: Horizontal Axis --> Label TAB --> Label Rotation --> 45 (the Label Rotation choice is under the big white box for entering the Label value) and Horizontal Axis --> Values TAB --> Value Rotation --> 45 (The Value Rotation choice is directly underneath the drop down box for selecting a Font for the Values) You may have to contact Tech Support to find out how to do this in EG 3. I -thought- the rotation option was also available in the Task Window in EG3. cynthia ... View more

When you run import wizards in Enterprise Guide, it can "see" your PC and pick up the data. Unfortunately when you run the code as a Stored Process it's running on the Unix server, which doesn't know about your PC. We work around this by 1st FTPing the data to the Unix server and then using an INFILE statement to read it. ... View more

Thanks Olivier, that works perfectly. To SAS proper, I'm sure more experienced users probably wouldn't have a problem understanding this, but instead of the syntax intnx( 'month', date, 0) the Enterprise Guide help has the syntax example as intnx( 'month', date, 0, beg ) ... View more