1 - 10 of 15 results for 'Proc EXPORT'
Previous   |    1 , 2   |    Next >
Sort by:
Date | Relevance

2012-03-22

46074 - PROC EXPORT may wrap observations if data set is from PROC TABULATE- Usage Note

If an output data set is created from PROC TABULATE and PROC EXPORT is used to write this data set to an external delimited file, the observations may wrap. PROC TABULATE includes three default variables in the output ...

http://support.sas.com/kb/46/074.html, 28KB

2010-12-24

41933 - ADLM seen in MPRINT output of SASŪ log when PROC IMPORT or PROC EXPORT is inside a macro- Usage Note

The line ADLM; will be seen in the MPRINT output of the SAS log when PROC IMPORT or PROC EXPORT reading or writing a comma, tab or delimited file is inside a macro and the macro is executed. Here is an example of ...

http://support.sas.com/kb/41/933.html, 28KB

2010-12-08

41735 - How to control variable names when using PROC EXPORT with comma, tab or delimited ...

... the external file: proc export data=sashelp.class outfile='c:\temp\classnoheaders ... Height of Person' Weight='Weight of Person'; run; proc export data=newclass outfile='c:\temp\classlabel.csv ...

http://support.sas.com/kb/41/735.html, 31KB

2010-12-08

41735 - How to control variable names when using PROC EXPORT with comma, tab or delimited files- Usage Note

Beginning in SAS 9.2, you can use the the PUTNAMES= statement with PROC EXPORT to control whether or not variable names are written out to comma, tab or delimited files. You can also use the PUTNAMES= statement with ...

http://support.sas.com/kb/41/735.html, 31KB

2009-09-18

3610 - "ERROR: Cannot open X display" when running PROC EXPORT or PROC IMPORT in batch mode- Usage Note

If you run PROC EXPORT or PROC IMPORT steps in batch mode in UNIX environments, you will receive the following error: ERROR: Cannot open X display. Check the name/server access authorization. The process might ...

http://support.sas.com/kb/3/610.html, 26KB

2009-02-18

34709 - The EXPORT procedure in Base SASŪ does not recognize case sensitive tablenames- Usage Note

When using Base SAS, PROC EXPORT does not recognize case sensitive tablenames and might return an error. If you use PROC EXPORT to write a case-sensitive database tablename to a delimited text file, use the name ...

http://support.sas.com/kb/34/709.html, 28KB

2007-09-12

20919 - ERROR: File Name value exceeds maximum length of 201 characters- Usage Note

The maximum file name length for OUTFILE= in PROC EXPORT is limited to 201 characters. Specifying a path with more than 201 characters will generate the following ERROR in the log: ERROR: File Name value exceeds ...

http://support.sas.com/kb/20/919.html, 27KB

2004-08-24

6030 - Export to Excel does not honor the SAS option MISSING- Usage Note

If you use: options missing=0; and then use the Export Wizard or PROC EXPORT to write a SAS dataset to the Excel file format, the missing values in the data set will be missing in the new file format, rather than ...

http://support.sas.com/kb/6/030.html, 26KB

2000-09-20

2432 - DAO Error Encountered with Proc Import/Export- Usage Note

The following error may be generated when trying to run PROC IMPORT or PROC EXPORT: ERROR: DAO Error encountered. To circumvent, install MDAC 2.5. MDAC is Microsoft's Data Access Components and can be downloaded ...

http://support.sas.com/kb/2/432.html, 25KB

1999-03-18

490 - ERROR: Invalid Sequence of Commands for file LIBREF.XXX.DATA- Usage Note

When using the IMPORT/EXPORT wizards or the PROCEDURE equivalents (PROC IMPORT/PROC EXPORT) to convert a DBF file to a SAS dataset, you may receive the following error: ERROR: Invalid sequence of commands for file ...

http://support.sas.com/kb/00/490.html, 25KB

1 - 10 of 15 results for 'Proc EXPORT'
Previous   |    1 , 2   |    Next >