Hi Alan, I think I understand and agree with your position, however I am not sure that we are aligned on what the problem actually is. I don't and never expect SAS to miraculously work universally or with bad data or poorly crafted code. What I expect (and perhaps this bears repeating) is that SAS is capable of releasing a PC file after an error is encountered/detected by SAS. That is it. Nothing more. It shouldn't take disconnecting from the SAS server or restarting SAS Studio or EG to free the file up. If you're wondering (and I doubt you are) why I am so hung on his issue, well it's three-fold: 1. I can't prevent the Excel files that I import from always being 100% compatible with the PROC IMPORT WHERE clause. I can certainly try (and will), but there is no guarantee it won't happen. 2. Similar to #1, I can't always ensure that the PROC IMPORT WHERE clause will be aligned the filtered column type. The vast majority of the time, they are (aligned). 3. Most of my EG projects are designed to set up the environment macro variables, libraries, etc. based on a user prompt response and other system variables. Each time an external file is lock and I have to disconnect or restart and when I do I lose all of the environment settings; which takes time to reset and present additional opportunity for entry error. No response is required and I very much appreciate you take time out for your day(s) to help me. At this point, I am not looking for a solution cause it sounds like one isn't available (aside from not getting the SAS error) and we can officially close this track. ... View more

Why would FILEEXISTS() not work because of the NOXCMD option? It seems to work for me. 1 %put %sysfunc(getoption(xcmd)); NOXCMD 2 %put %sysfunc(fileexist(~/autoexec.sas)); 1 ... View more

Thank you kindly for responding to my issue.   In EG, I have a handful of libraries that registered in the metadata but are not preassigned.  In order to assign them, I need to manually do so by right clicking on the library icoon in my server list.    The LIBNAME _ALL_ LIST command picks up all libraries whether they're assigned or not.  The solution provided by BallwardW solved my issue. Thank you very much, Michael ... View more

Since it seems thay you have successfully loaded a MS Access table, and use explicit SQL pass-thru, this not really a SAS question? An alternative approach would be to use the DBKEY= option together with SQL implicit pass-thru (that is using SQL that refers to your MS Access data using a libref). That could work well if your table Prov_Benefit_Plan_Mapping is quite small. /Linus ... View more

Vince, thank you again for all of your excellent support. I think my current solution, albeit not perfect, will meet my customer's needs and at the same time minimize the amount of additional development time that is required. The re-sizing of Excel columns was more of "nice-to-have" if it was something simple to code. Since my VB macro does exactly what I need it to do, all I have to do is figure out how to share my macro with the handful of users that will be running the process. That being said, I am sure that your suggestions and papers will be relied upon heavily in the future! Thanks again, Michael ... View more

I think I have figured out what I needed to do to accomplish my objective. I borrowed and adapted the snippet of code from a SUGI paper: http://www2.sas.com/proceedings/sugi31/066-31.pdf data InRTF; infile "path\filename.rtf" missover length = l end = lastobs lrecl = 2000; input line $varying2000. l; line=tranwrd(line, '{\field{\*\fldinst SYMBOL 179 \\f "Symbol" }}', '>='); line=tranwrd(line, '{\super a} ' , ''); if _n_=55 or _n_=56 then delete; run; data _null_; file "path\filename.rtf" dsd; set InRTF ; put line; run; */ ... View more

Thanks Scott. Great suggestion. I will definitely keep that in mind down the road. Shortly after posting my issue, I figured out what my problem was (I was using single quotes when I should have used double quotes). That simple oversight ultimately did the trick! Thanks for responding so quickly. ... View more

Hi, depending on which server your STP is running (workspace vs. stored process server) it will use a different user. Probably this could cause the error(s) you receive? br Thomas ... View more