As @SASKiwi says, I think you're only going to get trouble if you allow single quotes in the Group name.   However, maybe as a temporary work around you could try coding a %BQUOTE around the Group name.  I still think you may have trouble though down the road.  Use at you own risk.   "<UpdateMetadata> <Metadata> <Person Id=%str(%')&PersonId%str(%')> <IdentityGroups Function=&FUNC> <IdentityGroup ObjRef=%str(%')&GroupId%str(%') Name=%str(%')%BQUOTE(&Group)%str(%')/> </IdentityGroups> </Person> </Metadata> <ReposId>$METAREPOSITORY</ReposId> <ns>SAS</ns> <flags>268435456</flags> <Options/> </UpdateMetadata>"; Jim ... View more

The first thing I would check is:  Is the file open?  If the file is open and in use by another user, SAS may not be able to read it.  This is certainly the default behavior for SAS with Excel, so I assume this is also true with Access.   Jim ... View more

As long as the %PUT is before the Sort, then it is correctly placed.  SAS can be odd sometimes in terms of when it writes what to the log.  We're just going to have to play with it a bit.  We should see if you're options are set to WRITE=IMMEDIATE, which may help, and we can try moving the %PUT to inside the Proc Sort, before the BY statement.  Placement may make a difference; I don't know; I'm just trying things here.   Lastly, we could make the %PUT statement write multiple lines which may force SAS to write it out sooner, depending on how much SAS is buffering the log (assuming that SAS is buffering).   In order to tell whether you are operating under WRITE=IMMEDIATE or WRITE=BUFFERED, please run the following and post the log: PROC OPTIONS OPTION=LOGPARM; RUN; Jim ... View more

@tampham92 wrote: I already added that SQL_SAS datasource into the ODBC Datasouce Administrator but it still did not work. If you're using ODBC, you need to say "Connect to ODBC..." not "SQLSVR".   Try the below code (fix the password and such first of course).   Jim proc sql; connect to ODBC as mydb (datasrc="SQL_SAS" user="XXX" password="XXX"); select * from connection to mydb (select * from DATA_TABLE); quit; run; ... View more

Have you tried:     You should be able to automatically write to wherever you like as a step in the project.   Jim ... View more

OK, excellent, thank you.  I don't see anything obvious that is wrong.   Now, can you post the log?  Please, as you are with the SAS programs (thank you!), use the below indicated icon to post the log. There should be some messages that precede the %PUT statement, something like    DEVJJKCT assigned sucessfully   There should also be some SAS generated statements after the Format procedure.     If the above normal log information is present, then we know that the log is working up to the point where the %PUT occurs.   Jim ... View more

There's probably an error of some kind higher up in the code, possibly a missing semi-colon.  Can you post more of your code?   If your log is in color (i.e. not a batch job), you can make the %PUT statement stand out more by adding the text, "NOTE:" before it.  See example, below.  This will colorize the text to a sort of light blue which will make it easier to spot.  Probably it's not working, just as you say, but sometimes it's just hard to spot.   Jim   %put NOTE: SORT ED DATA BY KEYVAR; proc sort data = ED_DATA; by KEYVAR; run; ... View more

The warning is not a serious one, and the warning is not related to the encoding problem that you are seeing.  The real problem is the encoding and not the Varchar.     I'm not sure this is a bug; I think the configuration just needs to be adjusted.   Since you have two SAS versions available, what is the encoding on your older (M2) version of SAS versus your newer (M5) version of SAS?     Jim ... View more

It would be helpful if you could show more of your log using the indicated icons: Often, it's not serious when you get a "VARCHAR data type is not supported by the V9 engine" message in the log.  Usually, SAS just converts it to Char.   What are your results like?  Is there a problem with the results or is the message the only issue?   Jim ... View more

As far as I know that cannot be done.  You might be able to do it if you were willing to write a custom task using I believe C#.  @ChrisHemedinger might have a more authoritative answer.   Jim ... View more

OK, that makes sense.  That's why I was asking if anything had changed with the environment.  Turns out I was right.  🙂   Jim ... View more