Sorry, I was too quick there. %str can cause some problems in other situations too, bot can often be resolved by using %unquote. Does this work for your situation? It seems to work with your example. /Linus ... View more

%str() works fine in procedure calls. I think you have to check your PROC PRINT syntax instead... I guess that your OUT= should be DATA=. /Linus ... View more

Maybe this sample can help you out: http://support.sas.com/kb/26/065.html /Linus ... View more

Maybe you could execute the %abort conditionally according to a macro variable that is set by the calling job. /Linus ... View more

If you like you can use SQL as well, just add a count distinct for each of your columns. Not sure though how PROC SQL will process this internally regarding to efficiency. /Linus ... View more

I have no problem adding long expressions, as long as I use carriage returns in my code. /Linus ... View more

Some information is unclear to me: What do exactly mean by "In the physical storage of my table..."? Do you wish to continue to use user/pass from config, or use the ones registered in the metadata? If you wish to use metadata passwords, you have to them in sync, and the re-generate your code upon change. /Linus ... View more

For search paths, use the pathname() function. For other information (including search paths) use SASHELP.VLIBNAM view. /Linus ... View more

You are most likely running into having some special char echoed from your workspace server, which interrupts the communication. This could rely on what encoding you are using. Search on "TRANSCODE" on support.sas.com. See if can somthing there which applies to your situation. If not, open a track to SAS tech support. /Linus ... View more

You probably already have your local SAS defined as an EG meta server. You need the SQL Server ODBC driver locally (most probably installed by default). In the ODBC manager you have to define your data source using this driver. In EG, I think you just have to define a Library using a Wizard under Tools. For details se EG documentation. Linus ... View more

A search on "calculate integral" on support.sas.com gave me 136 results. I'll bet you can find some useful information there. Regards, Linus ... View more

To give you some advice we need to know your setup in more detail. Does your license for ACCES to ODBC apply to your SAS server license? Is your SAS server a metadata/workspace server implementation? I don't think there any big difference in performance between OLE DB and ODBC. And the best solution is probably to have your connection to SQL Server on your SAS server if any processing spills over to SAS, or you want to store some large intermediate results. /Linus ... View more

Macro variables will not change during data step execution, therefore does not your code work. Your example has only two variables to chose between. The easiest is just to hard code an IF-statement. If you in you real life has tons of columns, you may want to build something more generic. If you for instance can have a name standard for you analysis column, maybe you can generate a SELECT/IF/CASE statement as a macro pre-process using table metadata. /Linus ... View more

You could also consider to use SET with the KEY option, if you are having your zipcode table indexed. Another approach could to read the file with a data step view, then do an inner join to the zipcode table. /Linus ... View more

In the surrounding query (where you have sum(bfr.xxxxx) you cannot refer to bfr, the column will refer to the result of the inner query, which does not cary any bale name, or alias. So remove bfr. in the outer query, or add an alias bfr after the from (....) . /Linus ... View more