Also, from scanning Internet references on exporting B2020 data, it appears that "*.dbf" (dBase) is a popular format and there are some restrictions for other exported-data formats. Using the SAS support website http://support.sas.com/ I found this link with a sample for importing DBF format data:
We actually tried every single "save as" option available and got varying results. The biggest problem is that SAS does not like the variable names (some very long with many symbols) from 20-20. The file type they suggested was the *.csv. We've had some success viewing this in other programs but cannot get SAS to accept it.
It is just data. Based on what we have done so far leads me to believe that we will have to re-code all of the variable names (100's) in the import. This is feasible, but if someone has already done this (which there is no way someone hasn't), it would be great to hear their method. This is not a SAS problem, rather a lack of capacity to format in Beyond 20-20 (due to legitimate privacy protection).
Like I mentioned, since you haven't heard from anyone (yet) who has done the Beyond 20/20 to SAS data transition, it may be useful to get others' technical feedback based on some specifics about your files, data-layouts, variable-name challenges, and so on. If that other type of feedback isn't of interest to you, that's cool. There are many individuals on these forums willing to help, but more detailed information about the problem and the challenge would be useful.
That is very good advice. I'm going to wait a few days to see if I can get a response from someone in Canada actively using the software responds. After that, I'll figure out exactly what the issue is and post a much more specific question.