The log looks like you don't have any end-of line marker in the .csv file to separate the different records. Look at the "pampel's" at the end of the second data line; that looks like the same fixative as in the beginning of the first line. ... View more

Are you sure you are working with Enterprise Guide? "Fact Table Lookup" is not a construct in EGuide. ... View more

I'm surprised you got that warning message. Did your "real" job use single quotes or double quotes? If a string with a leading "&" is enclosed in double quotes, SAS tries to resolve it as a macro variable. If the same string is in single quotes, it leaves it as is. ... View more

And one of the things that changed in 9.2 is the syntax. So, if you are considering going to 9.2 soon you may want to compare the documentation so fewer things "break" when you do the upgrade. ... View more

See this thread from January on how to accomplish the same thing with EG 4.1 and SAS 9.1.3. http://support.sas.com/forums/thread.jspa?messageID=9148⎼ ... View more

I agree with Cynthia, it;s the logic. Multiple "or"s are notorious for causing this sort of conundrum. If ANY of the variables =1 means program participation, then the first statement is correct. If you have NO missing data, you can get the non-participation by changing he OR's to AND's, viz: if v2509 = 1 or v2510 = 1 or v2511 = 1 or v2512 = 1 or v2513 = 1 or v2514 = 1 or v2515 = 1 or v2516 = 1 then program_participation = 1; if v2509 = 0 AND v2510 = 0 AND v2511 = 0 AND v2512 = 0 AND v2513 = 0 AND v2514 = 0 AND v2515 = 0 AND v2516 = 0 then program_participation = 0; run; However, most of us have to contend with missing data. These sort of variables are often scored as a 1 if any are 1, and a 0 if any are checked and no 1's, and a missing only if all are missing. If you want that scoring, then the MAX function is the key: program_participation=MAX(OF v2509-v2516); as it returns a missing only if all elements are missing. Doc ... View more

Caitlin, The syntax is correct (except for the missing semi-colon). The mean function, used in a data step, requires that both the values are present for each observation to get a non-missing result. I wonder if you are really asking a different question, and looking for the mid-range ( http://en.wikipedia.org/wiki/Midrange ) of all observations in a set? If so, you may need to attack it differently: 1) PROC MEANS to output the min and max. 2) DATA step on the output to get the mid-range. Doc ... View more

Joshua, Chris's blog entry (above) has your answers to version compatibility. Doc ... View more

A couple of things. The "max query time restrictions" may not be related to the distance from the DB server, so a SAS server may not solve that problem. If the SAS server is down, no one can work. The cost should include back-up hardware. ... View more

This is probably a better question for the Enterprise Guide forum. EG is a client of SAS. It will not run without SAS also running somewhere to do the analyses. EG uses more than just the SAS Foundation to get it's work done (particularly useful are SAS/Stat and SAS/Graph), though it will run with just the SAS Foundation available. SAS 9.1.3 SP 4 and above will run with Vista. EG 4.1 has just been released with a Vista-aware install package (The older EG 4.1 will run under Vista, but the installation is a bit of a pain.). As far as other OS installations, look in the SAS product installation documentation on support.sas.com. It specifies which versions of which OS have been tested for installation. You can sometimes install on other version of the same 'family' (e.g. many people run SAS 9.1.3 on XP Home, even though XP Pro is the supported OS, but there are no guarantees). ... View more

StatTransfer also works well for converting the datasets. ( http://www.stattransfer.com/ ) We moved to that for general conversions because DBMS Copy is no longer being maintained. ... View more

Andrew, Has your copy of LE expired? I'm not sure how to check that, but LE has an expiration date that is different from regular SAS. Under EG 3.x, I've seen students have this problem when XP has marked the directory or file as 'read only' (under properties). Doc ... View more

I think that your error is that you are missing a "connection to" clause in the first select statement. Without it, SAS thinks that BDMIS is a SAS dataset in the WORK library. I would have expected this to have failed the same way on Windows. proc sql; connect to sqlsvr as BDMIS (datasrc="BDMIS" user=sasuser password=XXXXXXX); create table temp4.FACT_BASE as select * from connection to BDMIS (SELECT * FROM FACT_BASE WHERE &wherefmt); quit; The database specific syntax is described in the SAS Access documentation. This code uses the "pass thru" syntax for SQL. Did you get an error on the "connect to" statement? If so, you may have a bigger problem. Microsoft SQLserver is only supported via the ODBC connectivity in SAS 8.2 and above. So a simple copy of the program to Solaris will not get you running. You will also need the SAS/Access to ODBC product for Solaris and the appropriate system connections to get to the SQLserver database. [If you are connecting to the Sybase product, you may be OK.] ... View more

Cindy & SASman, The Enterprise Intelligence Platform is not necessary to use SAS/Access for Oracle (or, at least, I don't think that we have it installed). SASman, you will need to work with your Oracle DBA to get the information to use SAS/Access for Oracle. The schema name is defined in the tnsnames.ora file (a file that the DBA manages). You also need to have the appropriate Oracle client (or at least some pieces) installed on the machine that SAS is running on. Doc ... View more

Kamal, There is nothing in the SAS 9.1.3 online documentation that matches that phrase, so you'll need to provide more context to your question to get a useful answer from the forum. Doc ... View more