How to define the attribution of variables in proc import

[Reeza]

Did you run the macro code/compile it first? Also, not sure it will run in EG, this was designed for Windows and X command options which are often disabled in EG. You hadn't mentioned that you were using EG prior to this 😞

[leehsin]

I found my mistake for the text error and corrected it. Then it came out that:
options noxwait noxsync;
_______
13
ERROR 13-12: Unrecognized SAS option name NOXWAIT.

28 ! options noxwait noxsync;
_______
13
ERROR 13-12: Unrecognized SAS option name NOXSYNC.

This is because of using SAS EG, right? Thanks.

[Tom]

I doubt it is because of EG.  What version of SAS is your EG session connected to? What type of server is it running on?

Is it a Windows machine?

683   proc options option=xsync option=xwait;run;

    SAS (r) Proprietary Software Release 9.4  TS1M5

 XSYNC             Windows commands execute synchronously with SAS.
 XWAIT             The DOS shell closes and returns to SAS after EXIT is entered on the command line.
NOTE: PROCEDURE OPTIONS used (Total process time):

Or a Unix Machine? 

1447  proc options option=xsync ; run;

    SAS (r) Proprietary Software Release 9.4  TS1M5

ERROR: Unrecognized SAS option name XSYNC.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE OPTIONS used (Total process time):
      real time           0.05 seconds
      cpu time            0.00 seconds



1448  proc options option=xwait ; run;

    SAS (r) Proprietary Software Release 9.4  TS1M5

ERROR: Unrecognized SAS option name XWAIT.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE OPTIONS used (Total process time):
      real time           0.04 seconds
      cpu time            0.00 seconds

Or something else? 

Perhaps you are using a CAS server instead of regular SAS?

[leehsin]

It's EG 7.1 connected to a linux server.

[SyidaRox]

@leehsin - Did you ever resolve this issue?  I am experiencing the same problem and would love to know a solution.

[Kurt_Bremser]

What exactly is your issue? This thread has dealt with quite a lot, and is also more than a year old. You may get more responses by posting your question in a new thread.

[Reeza]

@SyidaRox the answer is the same, Excel does not enforce types in columns so there's no guarantee of types within an Excel file, it is not a RDBMS. 

SAS does not offer ways to specify the variables, but you can convert them after the fact. 

Converting your file to a CSV allows you to have full control over the import.

[ChrisNZ]

The only way you can hope SAS might read the values correctly is to set the data types in Excel: Text or Number or Date.

Still, Excel enforces no metadata, so you can never be sure.

[Tom]

Can you create and post a small example of an XLSX file that exhibits the issue you are having?

That is one where PROC IMPORT does not properly create a numeric variable from a column where every cell is numeric?

[leehsin]

These files contain sensitive data. I am not sure if I can create a small sample. I can try to replicate one and if I made it, I will post the sample. I guess the excel files generated have some internal attributions changed which was caused by the website that was modified by the owner, though these changes can not be seen by users.