most recent 30 from http://www.runsubmit.com 2010-09-09T12:24:32Z http://www.runsubmit.com/feeds/user/21 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://www.runsubmit.com/questions/362/running-source-code-stored-in-a-dataset/364#364 Alan Churchill 2010-08-24T23:46:30Z 2010-08-24T23:46:30Z

<p>I would put it out and bring it back (not tested).</p> <pre> data _null_; file 'c:\temp\test.sas' mod; set mydata.test; put 'data mylib.processd;' / codeVar / 'run;' // ; output; run; %include 'c:\temp\test.sas'; </pre> <p>This also allows you to see what it is creating and make sure it is correct.</p>

http://www.runsubmit.com/questions/347/accessing-sas-dataset-through-odbc-sas-localprovider/349#349 Alan Churchill 2010-07-29T01:06:16Z 2010-07-29T01:06:16Z

<p>The local provider does not permit SQL queries of any kind.</p> <p>You have several choices:</p> <p>a) Purchase Integration Technologies<br> b) Purchase SAS/intrNet<br> c) use my data management utilities (free) which do a delimited and XML conversion and allow queries<br> d) use my sas dataset binary reader/writer<br></p> <p>I work in C# though and do not (and will not) support VBA beyond its support of managed code.</p> <p>Alan C</p>

http://www.runsubmit.com/questions/269/installation-freezes/272#272 Alan Churchill 2010-06-01T05:16:27Z 2010-06-01T05:16:27Z

<p>Do an ALT-TAB and see if you have a dialog box hidden behind the installer.</p>

http://www.runsubmit.com/questions/120/what-differences-are-there-if-any-between-ole-db-and-odbc/121#121 Alan Churchill 2009-11-10T17:59:04Z 2009-11-10T17:59:04Z

<p>When given a choice, always pick OleDB. ODBC is the older access method that was replaced with OleDB. Speed-wise, they are about the same but oleDB has a lot less problems with drivers than ODBC does.</p> <p>Whenever I need the SAS syntax for an OleDB connection, I use my tool called SAS to SQL Converter (only runs on Windows, fyi).:</p> <p><a href="http://utilities.savian.net/" rel="nofollow">http://utilities.savian.net/</a></p> <p>It will call the Windows interface, allow you to make all of your choices and test your connection. It will then write the SAS libname statement for you. Hence, a GUI for doing OleDB connections.</p> <p>Alan</p>

http://www.runsubmit.com/questions/39/using-sas-base-to-import-data-from-tables-in-sql-server-using-odbc/40#40 Alan Churchill 2009-10-21T15:33:24Z 2009-10-21T15:33:24Z

<p>You need SAS/Access to OleDB or SAS/Access to ODBC. There are ways outside of that but it gets a lot more convoluted. If you absolutely ave to avoid that route, export as tab-delimited and bring it in that way. Formats are problematic. If you know .NET and C#, you can use my libraries to simplify it a bit. XML is also a choice.</p> <p>My SAS dataset reader is not ready so it isn't an option right now.</p> <p>Alan</p> <p><a href="http://www.savian.net" rel="nofollow">http://www.savian.net</a></p>