About jlt10f

jlt10f · ‎10-11-2023

In a related question... we were able to successfully import the file under Version 5, but the problem is now dealing with the missing data. Since R and SAS having different means of recording missings, what is the best method for retaining numeric variables from R when imported into SAS while having the missing properly coded in SAS?

jlt10f · ‎10-11-2023

It's not that large. It is only about half a MB. There are some long text responses which may be slowing it down, combined with the it being on the shared drive may be contributing to the long period of time.

jlt10f · ‎10-11-2023

Okay. They said they tried this and it results in taking an hour plus trying to read in the file, at which point they quit trying. Somone else suggested trying COMPRESS. I think it is some issue with the shared drive making everything take a very long time to import.

jlt10f · ‎10-11-2023

Okay. I will suggest this. Thank you for this suggestion and I will provide an update on this.

jlt10f · ‎10-11-2023

Unfortunately they will not allow anything to be copied off of the shared drive. I think the issue may be that it just takes a very long time to import anything off of the shared drive but I am not sure.

jlt10f · ‎10-11-2023

Thanks. I passed on this suggestion. I will follow up with any progress on it.

jlt10f · ‎10-11-2023

I think this is a good idea but there are not many R users in the organization and I think they want a more universal solution for people who are not R users.

jlt10f · ‎10-10-2023

This is the code that gave us the "File is not a SAS dataset" error (with filename and locations replaced) libname filename xport 'file location\filename.xpt'; data yourlibrary.dataset; set filename.filename; run; Then when that didn't work, we ran this and it was running for an hour before we cut it off: %xpt2loc(libref=work, filespec='c:\temp\trans.xpt') (again, with the appropriate filenames added) I think it may be important to mention that we are working on a shared drive and it is possible that is what is making it take so long, although other things were imported in a reasonable time period, so I am not sure.

jlt10f · ‎10-10-2023

I have exported an .xpt file from R using the haven package. My goal is to be able to create files that SAS users are able to import and use. I am able to import the file back into R without problem using the haven package. However, the SAS users are not able to successfully import the .xpt file into SAS. Is there something that can be done when exporting the .xpt that would make it easier to open in SAS as an .xpt. Conversely, is there anything that can be done in SAS to more easily open the .xpt file? I am an R user but have little knowledge of SAS. As a second challenge, this data is part of government work and has to be saved on a shared drive. When trying to import .xpt datasets from the shared drive, it takes a very long time. In addition to my initial question, is there any suggestion on what method would be the quickest?

Online Status	Offline
Date Last Visited	‎10-11-2023 02:32 AM

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

transporting files from R to SAS

transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

Re: transporting files from R to SAS

transporting files from R to SAS