"DATA is in a format that is native to another host", not solved by usual solutions

[bwg]

I know there has been several posts about this, I've read many of them, but sadly the solutions (mainly, using Unicode server) do not work and I still get the mistake as soon as I try:

DATA CIRCUIT.FVEALL;

set DATA CIRCUIT.FVE;

run;

Some variables contain text and it was written in French; could that be the issue? I tried to remove the variables, but I hit a wall as soon as SAS reads the dataset and get the error.

Do you think this is the issue? Not sure what else it could be. Also, what could I do to fix the issue or even to just remove the variables without getting the error?

Thank you!

EDIT: I have tried outencoding (moving library to new one), I have tried to rename file, nothing works on SAS 9.4 on my laptop; however, I have noticed that while I get the warning, it still works on another computer (using SAS 9.3).

[RyanK]

Need more info to help, first off, did you mean SET in the second line? Where/how was the original dataset created?

[bwg]

I apologize. It does have 'set' in the code.

I don't know how it was created; I was given the database. I was able to work on it on SAS 9.3 on a desktop in my lab yesterday. But it won't work on my laptop (SAS 9.4). 

For some reason that issue causes errors and thus I can't proceed with statistical analyses.

[ballardw]

Generally that message means that you are using a SAS data set that was created on a different operating system. Depending on the OS SAS will be able to use the data but it provides that message because it may take more time to process as a conversion takes place and sometimes there may be some slightly different results then if the file was used in it's native OS and SAS version.

This is not and error or mistake, just a notification.

The resulting data set FVEALL of

DATA CIRCUIT.FVEALL;

   set CIRCUIT.FVE;

run;

should not generate that message when used. You could overwrite the existing FVE by

DATA CIRCUIT.FVEALL;

   set CIRCUIT.FVE;

run;

DATA CIRCUIT.FVE;

   set CIRCUIT.FVEALL;

run;

which means future use of FVE shouldn't generate the message.

[bwg]

That's what I understood from reading about it online. However, I still get the 'error' message as soon as the first part of the code is read in SAS, thus this trick does not work for me.

I also tried to do 'outencoding' and it doesn't work either.

Despite the 'warning', I was able to perform some statistical analyses on another computer using SAS 9.3. However, it does not work on my laptop (SAS 9.4). I have tried using the Unicode Server and Unicode Support; both don't work.

I'm a bit at lost.

[ChrisBrooks]

Can you run the following proc code on your file and post the results here please

proc contents data=circuit.fve;
run;

This will tell us what operating system the file was created on and its encoding (although I don't think the encoding is the problem).

[saslove]

Where you create your library "circuit" , try this

library circuit "path" inencoding=any outencoding=any;

[Tom]

---

@bwg wrote:

That's what I understood from reading about it online. However, I still get the 'error' message as soon as the first part of the code is read in SAS, thus this trick does not work for me.

I also tried to do 'outencoding' and it doesn't work either.

Despite the 'warning', I was able to perform some statistical analyses on another computer using SAS 9.3. However, it does not work on my laptop (SAS 9.4). I have tried using the Unicode Server and Unicode Support; both don't work.

I'm a bit at lost.

---

If you are using different versions of SAS on different operating systems then you will definitely trigger the need to use CEDA engine to convert the files for you on the fly.  But you should not have any problems using the data.

You will have issues with format catalogs.  If you are using formats then either keep the source code and define the formats into WORK for each session that needs them.  Or create separate catalogs for each version/operating system combination that you are using and point your FMTSEARCH option setting to the correct catalog(s).

[RyanK]

If you have problems moving datasets between computers, trying using PROC CPORT to create a transport file.  If all else fails, dump the dataset contents to a flat file then reimport it.