Sorry. It looks like when I adapted my code to the cars dataset I didn't do it perfectly. Just trying to find a dataset users can run that creates wide column heights. It's fine with me if the text is truncated in places. I can refine the widths if needed. If there's a way to make it wrap and expand dynamically without the egregious extra space then all the better. ... View more

And here's log output for the code that works, again redacted.   1 %studio_hide_wrapper; 83 PROC EXPORT DATA=SASHELP.Class 84 OUTTABLE='test' 85 DBMS=ACCESSCS REPLACE LABEL; 86 DATABASE="<redacted but same as one that doesnt work >\DIRPS_birth_&YOI..accdb"; 87 SERVER="<redacted but same as one that doesnt work>"; 88 SERVERUSER='<redacted but same as one that doesnt work>'; 89 SERVERPASS=XXXXXXXXXXXXXXXXXX; 90 DBDSOPTS='INSERTBUFF=25'; 91 RUN; NOTE: "test" table was successfully created. NOTE: PROCEDURE EXPORT used (Total process time): real time 2.01 seconds cpu time 0.06 seconds   92 93 %studio_hide_wrapper; 104 105   ... View more

Here's the log.  I redacted some of it but please keep in mind I'm able to export a different SAS dataset to the same Access database using the same redacted information.  I appreciate your help with this!   1 %studio_hide_wrapper; 83 PROC EXPORT DATA=NAT_CERT_EXPORT 84 OUTTABLE='VV_NAT' 85 DBMS=ACCESSCS REPLACE LABEL; 86 DATABASE="<path redacted but works when exporting other SAS datasets>\DIRPS_birth_&YOI..accdb"; 87 SERVER="<server redacted but works when exporting other SAS datasets>"; 88 SERVERUSER='<user redacted but works when exporting other SAS datasets>'; 89 SERVERPASS=XXXXXXXXXXXXXXXXXX; 90 DBDSOPTS='INSERTBUFF=25'; 91 RUN; ERROR: A socket routine returned error: The connection was reset by a peer. ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: CLI execute error: Server communication failure. ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: CLI disconnect failed: Server communication failure. ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: A socket routine returned error: Broken pipe ERROR: CLI disconnect failed: Server communication failure. ERROR: Error in the LIBNAME statement. ERROR: Export unsuccessful. See SAS Log for details. NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE EXPORT used (Total process time): real time 3.21 seconds cpu time 0.10 seconds   92 93 %studio_hide_wrapper; 104 105     ... View more

Thanks for the response.  Yes, my URLs are not the same.  I'm using V.03.05   I'll contact my SAS administrator but I'm getting into an area I'm not familiar with.  I imagine there's a reason why the URLs don't match and it may not be possible or easy to make them match.  If the administrator can't make them match then does this mean I can't run a program from another program in Viya? ... View more

Thanks, Sajid01.  If running from the snippets folder is more complicated then I don't have any concerns about running from a non-snippets folder, but running from a non-snippets folders gives me the same error message.   ... View more

Thanks, BrunoMueller.  I ran your code and I can see the URL in the log doesn't match the URL I currently see in my session nor does this URL include anything that looks like a port number.  I'm not sure I know what to do with this information. ... View more

Thanks for the suggestion.  Sorry.  I was doing some masking so I doctored the image a bit.  I always use the insert as path option so case and path should not be the issue.   ... View more

Thanks, BrunoMueller.  I think this image includes everything you mentioned.       ... View more

Thanks for the reply BrunoMueller.  I moved my code to another folder but I'm still getting the same error message.  The error message indicates a problem with the path.  Whether I try the filename statement with or without referencing the SAS code I get the same message so I don't think this is about the file extension.  When I right click my program and select properties it has a sas extension and the type is SAS Program.     filename ffile FILESRVC folderpath='/Users/ryanb/My Folder/SAS_FILES' filename='program.sas'; %include ffile / source; filename ffile clear; ERROR: Folder denoted by path '/Users/ryanb/My Folder/SAS_FILES' was not found. ERROR: Error in the FILENAME statement.     ... View more

I looked up ls parameters and came across --full-time.  It generates output a little different than before but everything is now consistent.     filename pipedir pipe %sysfunc(quote(ls -lR --full-time "&pathDir" )) lrecl=1000; data DIR; infile pipedir truncover; input line $char1000.; run; ... View more

I'm very close but I'm getting some strange results: filename pipedir pipe %sysfunc(quote(ls -lR "&pathDir" )) lrecl=1000; data DIR; infile pipedir truncover; input line $char1000.; run; this code returns some values with the year and others with the time.  -rw-------. 1 ryanb domain users 40016 Aug 7 2023 FILENAME1.mor -rw-------. 1 ryanb domain users 40016 Aug 14 10:10 FILENAME2.mor It will provide one or the other but never both, at least in the sample I reviewed.   ... View more

Thanks!  Yes.  I was masking my path and pasted my example in the wrong format.  I appreciate you making that clear and for letting me know I don't need DIR or quotes in the command statement.  I pasted some code below that worked as you described.   filename pipedir pipe %sysfunc(quote(ls -lR /TEMP )) lrecl=1000; data DIR; infile pipedir truncover; input line $char1000.; run; ... View more