f



Re: MS Access and SAS datasets #4

MS Access also has a CAPTION field that behaves more like a SAS variable
label.  However, I have not found a way to write to that field from SAS.

Ed

Edward Heaton, SAS Senior Systems Analyst,
Westat (An Employee-Owned Research Corporation),
1600 Research Boulevard, RW-3541, Rockville, MD 20850-3195
Voice: (301) 610-4818                  Fax: (301) 610-5128
mailto:EdHeaton@Westat.com             http://www.Westat.com



-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
Howard Schreier <hs AT dc-sug DOT org>
Sent: Tuesday, May 24, 2005 11:21 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: MS Access and SAS datasets


Use PROC FORMAT with the CNTLOUT option to dump your formats.

I don't know about the labels. Access has a "Description" field in its
metadata structure, so it's reasonable to expect the labels to end up
there.

On Mon, 23 May 2005 14:01:18 -0800, David Neal <afdbn@UAA.ALASKA.EDU>
wrote:

>I'm trying to move several SAS datasets to a single MS Access database.

>When I use proc copy to move the data, I get the following note:
>
>
>
>NOTE: Copying SCFSAS.PT_MISC to SCFFAS.PT_MISC (memtype=DATA).
>
>NOTE: SAS variable labels, formats, and lengths are not written to DBMS

>tables.
>
>
>
>My problem is that I'm interested in keeping the variable labels and
>the formats as well.  Is it possible for SAS to automatically create
the "lookup
>tables" from the formats?  Also, is there a way to keep the variable
>labels when I move from SAS to Access?
>
>
>
>David Neal
0
EdHeaton (665)
5/24/2005 5:13:24 PM
comp.soft-sys.sas 142828 articles. 3 followers. Post Follow

0 Replies
406 Views

Similar Articles

[PageSpeed] 6

Reply:

Similar Artilces:

Re: combine n SAS datasets in to one SAS dataset. #4
<html> <body> <br> Filename allfiles ('d:\conv\2008*.asc');&nbsp; * Filenames can use wildcards;<br><br> infile allfiles;<br><br> <br><br> <br> At 10:53 AM 1/14/2009, b.djaby@gmail.com wrote:<br> <blockquote type=cite class=cite cite="">Hi,<br> I have a similar problem in my SAS macro;<br> I have many ascii files where name are&nbsp; 2008011.asc to 2008123<br> &nbsp;year = 2008, month=01 to 12 and dekad = 1 to 3;<br> To import all my files, I have writed 2 similars&nbsp; macro contain with<br> those code:<br> %LET month=9;<br> %LET dekad=3;<br> <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>%Do i= 1 %to &amp;month;<br> <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>%DO j = 1 %to &amp;dekad;<br> %let dataname =&quot;d:\conv\20080&amp;i&amp;j.asc&quot;;<br> infile &amp;dataname;<br> ****<br> and for second<br><br> %LET month=12;<br> %LET dekad=3;<br> <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>%Do i= 10 %to &amp;month;<br> <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>%DO j = 1 %to &amp;dekad;...

Re: Deleting SAS Data from a SAS DATASET #4
Summary: PROC DATASETS; AGE statement. + VIEWs This won't help you delete data from your very big data set, but you may find this example interesting. You say you append data monthly to a big data set then when big gets too big you need to clean out the old. And that takes a very long time. However if you don't physically append but use a view to append/combine you may find it easier to get rid of the unwanted old data. Consider this code. it pushes MonthlyUpdate onto the stack of 24 data sets and the 24th data set is deleted. Then all the data sets get renamed to produce a new group of 24. You can see from the notes how the operation works. The data sets don't have to use a numbered range M01-M24 I did that for my convenience. proc datasets library=work; age MonthlyUpdate m01-m24; run; quit; NOTE: Deleting WORK.M24 (memtype=DATA). NOTE: Aging the name WORK.M23 to WORK.M24 (memtype=DATA). NOTE: Aging the name WORK.M22 to WORK.M23 (memtype=DATA). NOTE: Aging the name WORK.M21 to WORK.M22 (memtype=DATA). NOTE: Aging the name WORK.M20 to WORK.M21 (memtype=DATA). NOTE: Aging the name WORK.M19 to WORK.M20 (memtype=DATA). NOTE: Aging the name WORK.M18 to WORK.M19 (memtype=DATA). NOTE: Aging the name WORK.M17 to WORK.M18 (memtype=DATA). NOTE: Aging the name WORK.M16 to WORK.M17 (memtype=DATA). NOTE: Aging the name WORK.M15 to WORK.M16 (memtype=DATA). NOTE: Aging the name WORK.M14 to WORK.M15 (memtype=DATA). NOTE: Aging the name WORK.M13 to WORK.M14 (me...

Re: SAS and MS Access #4
Peter, If you want to access the tables rather than copy the data to SAS, and you have ACCESS to PC Data Files licensed as Ari mentioned, you can use a LIBNAME statement. LibName yourMdb odbc complete="dsn=MS Access Database;dbq=your data file" ; You might have problems with names of tables and variables; Access is much more open about that than SAS. If so, try the VALIDVARNAME=ANY system option and name literals -- e.g. "Cost in $"n Ed Edward Heaton, SAS Senior Systems Analyst, Westat (An Employee-Owned Research Corporation), 1600 Research Boulevard, RW-3541, Rockville, MD 20850-3195 Voice: (301) 610-4818 Fax: (301) 610-5128 mailto:EdHeaton@Westat.com http://www.Westat.com -----Original Message----- From: Ari Toikka [mailto:toikkari@YAHOO.CO.UK] Sent: Thursday, May 06, 2004 2:27 AM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: SAS and MS Access Hi, if you have ACCESS to PC Data files licensed, you can use the import / export wizards (File / Import Data) You can then save the generated program, which might look for example like this: Proc import out = sasuser.test datatable="h456test" dbms =ACCESS97 replace; DATABASE="T:\h345test.mdb"; run; If you have columns in MS Access having a length over 1024 characters, you have to add: Memosize=xxxxxxx ; /* xxxxx=the maximum length */ Ari Toikka Statistics Finland Peter Hruby <hrubyp@SYMPATICO.CA> wrote:Hi SAS-L, I am wondering w...

Re: MS Access and SAS datasets
Use PROC FORMAT with the CNTLOUT option to dump your formats. I don't know about the labels. Access has a "Description" field in its metadata structure, so it's reasonable to expect the labels to end up there. On Mon, 23 May 2005 14:01:18 -0800, David Neal <afdbn@UAA.ALASKA.EDU> wrote: >I'm trying to move several SAS datasets to a single MS Access database. >When I use proc copy to move the data, I get the following note: > > > >NOTE: Copying SCFSAS.PT_MISC to SCFFAS.PT_MISC (memtype=DATA). > >NOTE: SAS variable labels, formats, and lengths are not written to DBMS >tables. > > > >My problem is that I'm interested in keeping the variable labels and the >formats as well. Is it possible for SAS to automatically create the "lookup >tables" from the formats? Also, is there a way to keep the variable labels >when I move from SAS to Access? > > > >David Neal ...

Re: Using SAS with large datasets (linking SAS and Access)
I have very little experience with using this but I have found that if you have SAS Access for PC Products licensed, just as you can issue a libname statement pointing to an Excel workbook, you can also issue one for an Access database. Try doing this and then look at your SAS explorer window where you will see an icon for the Access file and will then be able to look at the Access tables as if they were SAS data sets. Nat Wooding Environmental Specialist III Dominion, Environmental Biology 4111 Castlewood Rd Richmond, VA 23234 Phone:804-271-5313, Fax: 804-271-2977 ben.powell@CLA.CO .UK Sent by: "SAS(r) To Discussion" SAS-L@LISTSERV.UGA.EDU <SAS-L@LISTSERV.U cc GA.EDU> Subject Re: Using SAS with large datasets 06/23/2008 06:01 AM Please respond to ben.powell@CLA.CO .UK If you haven't already, export the data out of Access asap as mdb operations tend to be several orders of magnitude slower than SAS. Export to tab or csv and import into SAS. The export procedure from Access is relatively painless. If you've already done that and are still facing problems you should provide more info on variabl...

Re: MS Access and SAS datasets #2
Hi David - I agree with Howard that CNTLOUT will give you your formats to develop lookup tables in Access. Alternately if your data isn't large and you don't care about normal form, you could process your variables through your formats with put statements and create parallel formatted data. In v9 there's VLABEL, VLABELX, and VARLABEL, etc. You can use VLABEL and array all your _numeric_ and then _character_ columns and create a label dataset. There's also the data dictionary which you can query and use the into: command to load a macro, or just dump the labels in a dataset. Personally, I like to use "options VALIDVARNAME=ANY;" and rename my variables as their labels before I port data to external databases, but I'm an analyst, not a programmer, and I can hear several mavens groaning in the distance as I write this. ;-) Good luck and hth - Paul Choate DDS Data Extraction (916) 654-2160 On Mon, 23 May 2005 14:01:18 -0800, David Neal <afdbn@UAA.ALASKA.EDU> wrote: >I'm trying to move several SAS datasets to a single MS Access database. >When I use proc copy to move the data, I get the following note: > > > >NOTE: Copying SCFSAS.PT_MISC to SCFFAS.PT_MISC (memtype=DATA). > >NOTE: SAS variable labels, formats, and lengths are not written to DBMS >tables. > > > >My problem is that I'm interested in keeping the variable labels and the >formats as well. Is it possible for SAS to automatic...

Re: MS Access and SAS datasets #6
You are right, the "slightly" was an understatement on my part.(I guess I was being nice.) I believe ACCESS is limited to 256 (or 255 I forget which) columns so I am required to do a bit of reshaping anyway. I will be working with(reshaping) the data in SAS and then move it into ACCESS. I feel much more comfortable tweaking it in SAS and then moving it to ACCESS. David -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Howard Schreier <hs AT dc-sug DOT org> Sent: Tuesday, May 24, 2005 5:26 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: MS Access and SAS datasets I suspect that you don't need a "slightly" different approach. You probably need a significantly different one. Wide tables are clumsy to work with in SAS, but I think in Access the problems will be much more severe. I would think that the occasion of a port from one platform to another provides the opportunity to reshape and streamline. You will probably find it easier to do this before porting, rather than after. On Tue, 24 May 2005 09:26:21 -0800, David Neal <afdbn@UAA.ALASKA.EDU> wrote: >Thanks for the input. Unfortunately, the datasets are quite wide. One >of them, for example, has over 1000 variables (columns). Had I been >involved with the creation of the initial SAS datasets, I would have >suggested a slightly different approach. Since this wasn't the case, >I'm stuck working with things the way they...

Re: MS Access and SAS datasets #5
I suspect that you don't need a "slightly" different approach. You probably need a significantly different one. Wide tables are clumsy to work with in SAS, but I think in Access the problems will be much more severe. I would think that the occasion of a port from one platform to another provides the opportunity to reshape and streamline. You will probably find it easier to do this before porting, rather than after. On Tue, 24 May 2005 09:26:21 -0800, David Neal <afdbn@UAA.ALASKA.EDU> wrote: >Thanks for the input. Unfortunately, the datasets are quite wide. One >of them, for example, has over 1000 variables (columns). Had I been >involved with the creation of the initial SAS datasets, I would have >suggested a slightly different approach. Since this wasn't the case, >I'm stuck working with things the way they are. To complicate things, >ACCESS won't handle tables that wide so I'm having to mess with he data >anyway. Your (and Howard's) suggestions will at least get me going on >the right path. (Maybe I'll just round up some "slave" labor, AKA a >graduate student, to set up all the lookup tables in ACCESS.) > >Thanks again > >David Neal > >Choate, Paul@DDS wrote: >> Hi David - >> >> I agree with Howard that CNTLOUT will give you your formats to develop >> lookup tables in Access. Alternately if your data isn't large and you >> don'...

Re: MS Access and SAS datasets #8
Does SQL Server Express have a lot of proprietary extensions to the SQL language which provide array processing and the like? If not, the column capacity may be more a curse than a blessing. I don't know the specifics of David's project, but based on experience I suspect that a lot of normalization is possible, and that if it is done, even the capacity of Access will be far more than adequate. On Tue, 24 May 2005 20:07:03 -0600, Alan Churchill <SASL001@SAVIAN.NET> wrote: >David, > >I believe SQL Server Express (which is free) can handle 1024 columns. You >may want to consider that approach if you have to move it anyway. > >Thanks, >Alan > >Savian >"Bridging SAS and Microsoft Technologies" > >-----Original Message----- >From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of David >Neal >Sent: Tuesday, May 24, 2005 6:54 PM >To: SAS-L@LISTSERV.UGA.EDU >Subject: Re: MS Access and SAS datasets > >You are right, the "slightly" was an understatement on my part.(I guess I >was being nice.) >I believe ACCESS is limited to 256 (or 255 I forget which) columns so I am >required to do a bit of reshaping anyway. I will be working with (reshaping) >the data in SAS and then move it into ACCESS. I feel much more comfortable >tweaking it in SAS and then moving it to ACCESS. > >David > >-----Original Message----- >From: SAS(r) Discussion [mailto:SAS-L@LISTS...

Re: MS Access and SAS datasets #9
Howard, I completely agree on fixing the normalization issue. Oftentimes though it is something that has to be done later. SQL Server Express has the .NET CLR built-in which means that you can use most .NET code in the SQL expression. Regardless of whether this is a proprietary extension (which it is...a LOT), Access is a less than optimal database. However, it will probably work as you suggest with some work on normalizing the structure. Thanks, Alan Savian "Bridging SAS and Microsoft Technologies" -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Howard Schreier <hs AT dc-sug DOT org> Sent: Tuesday, May 24, 2005 8:48 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: MS Access and SAS datasets Does SQL Server Express have a lot of proprietary extensions to the SQL language which provide array processing and the like? If not, the column capacity may be more a curse than a blessing. I don't know the specifics of David's project, but based on experience I suspect that a lot of normalization is possible, and that if it is done, even the capacity of Access will be far more than adequate. On Tue, 24 May 2005 20:07:03 -0600, Alan Churchill <SASL001@SAVIAN.NET> wrote: >David, > >I believe SQL Server Express (which is free) can handle 1024 columns. You >may want to consider that approach if you have to move it anyway. > >Thanks, >Alan > >Savian >"Bridging SAS and Microsoft...

Re: MS Access and SAS datasets #3
Thanks for the input. Unfortunately, the datasets are quite wide. One of them, for example, has over 1000 variables (columns). Had I been involved with the creation of the initial SAS datasets, I would have suggested a slightly different approach. Since this wasn't the case, I'm stuck working with things the way they are. To complicate things, ACCESS won't handle tables that wide so I'm having to mess with he data anyway. Your (and Howard's) suggestions will at least get me going on the right path. (Maybe I'll just round up some "slave" labor, AKA a graduate student, to set up all the lookup tables in ACCESS.) Thanks again David Neal Choate, Paul@DDS wrote: > Hi David - > > I agree with Howard that CNTLOUT will give you your formats to develop > lookup tables in Access. Alternately if your data isn't large and you > don't care about normal form, you could process your variables through your > formats with put statements and create parallel formatted data. > > In v9 there's VLABEL, VLABELX, and VARLABEL, etc. You can use VLABEL and > array all your _numeric_ and then _character_ columns and create a label > dataset. > > There's also the data dictionary which you can query and use the into: > command to load a macro, or just dump the labels in a dataset. > > Personally, I like to use "options VALIDVARNAME=ANY;" and rename my > variables as their labels before...

Re: MS Access and SAS datasets #7
David, I believe SQL Server Express (which is free) can handle 1024 columns. You may want to consider that approach if you have to move it anyway. Thanks, Alan Savian "Bridging SAS and Microsoft Technologies" -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of David Neal Sent: Tuesday, May 24, 2005 6:54 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: MS Access and SAS datasets You are right, the "slightly" was an understatement on my part.(I guess I was being nice.) I believe ACCESS is limited to 256 (or 255 I forget which) columns so I am required to do a bit of reshaping anyway. I will be working with(reshaping) the data in SAS and then move it into ACCESS. I feel much more comfortable tweaking it in SAS and then moving it to ACCESS. David -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Howard Schreier <hs AT dc-sug DOT org> Sent: Tuesday, May 24, 2005 5:26 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: MS Access and SAS datasets I suspect that you don't need a "slightly" different approach. You probably need a significantly different one. Wide tables are clumsy to work with in SAS, but I think in Access the problems will be much more severe. I would think that the occasion of a port from one platform to another provides the opportunity to reshape and streamline. You will probably find it easier to do this before porting, rather than after. ...

Re: SAS/ACCESS
Does the DBMAX_TEXT option do what you want? http://support.sas.com/onlinedoc/913/getDoc/en/acreldb.hlp/a003113591.htm -- Jack Hamilton jfh@alumni.stanford.org Videtis illam spirare libertatis auram On Jan 22, 2009, at 8:57 am, Matthew Pettis wrote: > Hi, > > > > I have a CLOB coming back from an Oracle passthrough query that is > >1024 > in length. How do I specify that my receiving variable in a SAS > dataset > be longer than 1024 characters to accommodate this? By default, I get > SAS thinking that this is 1024 characters, when it is really a CLOB > and > I want to set some large default length on this variable length... > > > > Thanks, > Matt ...

Re: SAS Formats
Hi Karan, Well, then you have a format catalog, in its specific format, of which you could make a SAS dataset using the (LIBRARY and) CNTLOUT option of PROC FORMAT. From the dataset you could try to generate text in the form of SPSS value labels. Maybe there are, but I don't know of it, other ways SPSS can handle SAS formats. It's been 9 years since I lastly used SPSS (four win does). Regards - Jim. -- Y. (Jim) Groeneveld, MSc., Biostatistician, Vitatron b.v., NL Jim.Groeneveld_AT_Vitatron.com (replace _AT_ by AT sign) http://www.vitatron.com, http://home.hccnet.nl/jim.groeneveld My computer always teaches me something new I thought I knew already. [common disclaimer] On Tue, 19 Jul 2005 15:17:42 +0530, Karan Bhatia <karan@ABSOLUTDATA.NET> wrote: >Hi Jim, > >Thanks for your prompt reply on SAS-L. > >I do not have formats as code, but as "formats.sasb7cat" which appears with >a icon of a folder with a red dot at lower right corner. I feel its similar >to a zip file. > >I know how to use formats code to convert it to SPSS value label code using >a text editor, but don't know how to use this. > >I am using SAS 8.2 and SPSS 12. > >Thanks, >Karan > >Karan Bhatia | karan@absolutdata.net; >AbsolutData Technologies Inc. | http://www.absolutdata.net >+91.11.5163.6400 Ext - 338 (Intl Dialing) >+510.903.1026 Ext - 338 (US Dialing) > > >-----Original Message----- >From: Jim Groeneve...

Re: Storing SAS-programs and -macros in SAS-datasets on a HOST-platform #4
SI provide an example of using a sas catalog as if it were a pds (as a "aggregate storage location"), in the onlinedoc at http://support.sas.com/onlinedoc/913/getDoc/en/lrdict.hlp/a000214504.htm#a00 0351123 (this is a 9.1.3 link, but the example is valid since before sas v8) However, sas catalogs don't (neccessarily) make cross/platform operations easier. A program is usually a lot smaller that the space it takes up in a sas catalog as a source entry. If you have a lot of programs, the proc upload or download time may become less welcome ;-) "Aggregate storage location&quo...

Re: SAS/ACCESS
DBMAX_TEXT does the trick; thank you all who helped! Matt -----Original Message----- From: Jack Hamilton [mailto:jfh@stanfordalumni.org] Sent: Sat 1/24/2009 1:42 AM To: Pettis, Matthew (Prof II&RS) Cc: SAS-L@LISTSERV.UGA.EDU Subject: Re: [SAS-L] SAS/ACCESS - Oracle: setting field lengths in SAS datasets returned from passthrough Does the DBMAX_TEXT option do what you want? http://support.sas.com/onlinedoc/913/getDoc/en/acreldb.hlp/a003113591.htm -- Jack Hamilton jfh@alumni.stanford.org Videtis illam spirare libertatis auram On Jan 22, 2009, at 8:57 am, Matthew Pettis wrote: > Hi, > > > > I have a CLOB coming back from an Oracle passthrough query that is > >1024 > in length. How do I specify that my receiving variable in a SAS > dataset > be longer than 1024 characters to accommodate this? By default, I get > SAS thinking that this is 1024 characters, when it is really a CLOB > and > I want to set some large default length on this variable length... > > > > Thanks, > Matt ...

Re: combine n SAS datasets in to one SAS dataset.
If you use the dictionary tables try Proc SQL - it will run much more quickly than a datastep: %let lib=YourLib; %let mem=file2007; proc sql noprint; select MemName into :MemList separated by " &lib.." from dictionary.tables where LibName=upcase("&lib") and MemType='DATA' and MemName eqt upcase("&mem"); quit; data &lib.File_History; set &lib.&MemList; run; hth Paul Choate DDS Data Extraction (916) 654-2160 -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of stulkem@YAHOO.COM Sent: Thursday, January 17, 2008 12:06 PM To: SAS-L@LISTSERV.UGA.EDU Subject: combine n SAS datasets in to one SAS dataset. Thanks for your help in advance! I have hundreds of SAS datasets that I want to combine into one SAS dataset. For example, I want to set file20070101.sas7bdat - file20071231.sas7bdat (365 total files) into file_history.sas7bdat. How can I write this into a macro or array or whatever will work so I don't have to write each individual file name?? Thanks again! Mark ...

Re: from SAS to MS Access without Proc Export #4
Hi Bill - I think you already have your answer - Access reads HTML files just as Excel does. HTML has no table size limits I'm aware of. Use ODS to create the HTML file and read the HTML file directly with MSAccess, skipping Excel. BTW isn't the 65k row limit in Excel absurd? regards Paul Choate DDS Data Extraction (916) 654-2160 -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Bill Droogendyk Sent: Monday, November 22, 2004 12:04 PM To: SAS-L@LISTSERV.UGA.EDU Subject: from SAS to MS Access without Proc Export Folks: I've an application running from my PC via SAS Connect to the Mainframe that harvests some MF data, downloads the data and uses proc export to build an MS Access file. Now and again, the app fails due to a glitch on our PC network. I'm doing it this way because we don't have proc export on the MF. I can produce xl files from the MF to the PC network with ODS, html and ftp. MS Access imports xl files quite readily, but xl files do have a size limit that we sometimes exceed.Is there also a simple "equivalent" way to produce (directly) ms access files with only SAS Base? Thanks, Bill ...

Re: How does SAS handle multiple sessions accessing a same dataset #4
Thank you all for your replies. I tested on windows SAS to read from a dataset, using a different libname and access=readonly option, while it is being updated by another SAS session. There is an error message: ERROR: A lock is not available for lib_2.testds.DATA, lock held by another process. ...

Re: R vs. SAS (was Replacement for SAS (SPSS vs. SAS, redux)) #4
No, sorry if I made it sound that way..... SAS and R are totally different in the way they work, how they are structured, what the statements look like, and so on. Not like French and Spanish, not even like English and Spanish. More like English and Swahilli. R has a lot in common with S Plus, both are based on the S language. But there is no hostility that I know of between S Plus and R (unlike the situation with Linux) Peter >>> <ben.powell@CLA.CO.UK> 2/5/2004 10:36:32 AM >>> wrote Sounds like R is the SAS equivalent of Linux .. who are incidentally in all sort...

Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. #4
Ed , I still contend and stick with they should both be able to program and know how SAS works. I prefer the intervewing company give a test, were the person being interviewed is sat in front a laptop or desktop and told to write code to solve some problems. No online help no books just the persona nd the computer. This weeds out those who can code and those who cant, from those who can you then talk to them about the code they wrote and you can deduce those who understand how SAS works and thos who dont. The pool you are left with are the qualified candidates atleast from a SAS perspective and you can make your choice from there. Toby Dunn Comprimise is like telling a lie, it gets easier and easier. Each comprimise you make, that becomes your standard. Perfection doesnt exist, once you reach it, its not perfect anymore. It means something else. From: Ed Heaton <EdHeaton@WESTAT.COM> Reply-To: Ed Heaton <EdHeaton@WESTAT.COM> To: SAS-L@LISTSERV.UGA.EDU Subject: Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. Date: Tue, 4 Sep 2007 16:52:16 -0400 Okay, I think I need to weigh-in on this. First, the exam is designed to test what you know about how SAS works. I think it does a fair job at that. (I say so partly because I only scored 89 on the exam. Now, I didn't prepare for the exam; I was really testing the exam when I took it as opposed to using the exam to test my skills.) The exam doesn't know how well you can program...

Re: combine n SAS datasets in to one SAS dataset. #3
Here's another option using julian dates: %macro julday(year); %do i=1 %to 365; data _null_; day=datejul(&year*1000+&i); date=put(day,yymmddn8.); call symput("yymmdd",date); put day= date=; run; %put yymmdd=&yymmdd; proc append base=file_history new=file&yymmdd.;run; %end; %mend; %julday(2007); At 11:44 AM 1/18/2008, Howard Schreier <hs AT dc-sug DOT org> wrote: >On Thu, 17 Jan 2008 12:06:01 -0800, stulkem@YAHOO.COM wrote: > > >Thanks for your help in advance! > > > >I have hundreds of SAS datasets that I want to combine into one SAS > >dataset. > > > >For example, I want to set file20070101.sas7bdat - > >file20071231.sas7bdat (365 total files) into > >file_history.sas7bdat. > > > >How can I write this into a macro or array or whatever will work so I > >don't have to write each individual file name?? > > > >Thanks again! > > > >Mark > >You must provide some rule or process which SAS can use to discover the >names of the data sets to be processed. > >Here is how I might deal with the example (one file for each day of a >calendar year): > > data _null_; > call execute('proc datasets library=mylib nolist;'); > call execute('delete file_history;'); > call execute('run;'); > do day = '01jan2007'd to '31dec2007'd; > call execute('ap...

Re: combine n SAS datasets in to one SAS dataset. #2
On Thu, 17 Jan 2008 12:06:01 -0800, stulkem@YAHOO.COM wrote: >Thanks for your help in advance! > >I have hundreds of SAS datasets that I want to combine into one SAS >dataset. > >For example, I want to set file20070101.sas7bdat - >file20071231.sas7bdat (365 total files) into >file_history.sas7bdat. > >How can I write this into a macro or array or whatever will work so I >don't have to write each individual file name?? > >Thanks again! > >Mark You must provide some rule or process which SAS can use to discover the names of the data sets to be processed. Here is how I might deal with the example (one file for each day of a calendar year): data _null_; call execute('proc datasets library=mylib nolist;'); call execute('delete file_history;'); call execute('run;'); do day = '01jan2007'd to '31dec2007'd; call execute('append base=mylib.file_history data=mylib.file' || put(day,yymmddn8.) || ';'); end; call execute('quit;'); run; ...

Re: SAS/access for Oracle and MS SQL server are different license? #4
Thanks Mary, We have SAS/Access to Oracle, because we need to access some oracle database from our partner. We don't have Oracle in house. We have SQL Server though. Actually, I would like to transfer SAS data to SQL server. I googled around, it seems that I can create CSV file then 'BULK' load to SQL server. -----Original Message----- From: Mary [mailto:mlhoward@avalon.net] Sent: Tuesday, April 28, 2009 1:11 PM To: Huang, Ya; SAS-L@LISTSERV.UGA.EDU Subject: Re: Re: SAS/access for Oracle and MS SQL server are different license? Given that you have SAS/Access to Oracle, how about buying Oracle :-) Seriously, it is not that expensive anymore. The other option I suppose would be to export SQL Server files as Excel spreadsheets or tab-delimited files, then run your SAS from those, but it would be tricky to do that. One trick might be to see if you could do a data link into an Excel spreadsheet to make that your front-end to the SQL tables that you want to use, then use the Excel methods of importing to SAS. -Mary ----- Original Message ----- From: "Ya Huang" <ya.huang@AMYLIN.COM> To: <SAS-L@LISTSERV.UGA.EDU> Sent: Tuesday, April 28, 2009 3:00 PM Subject: Re: SAS/access for Oracle and MS SQL server are different license? > Thanks Michael, > > But SAS/Access to ODBC or SAS/Access to OLE DB are also need to be > licensed right? Looks like we don't have them either. Are there other > options? > > > On Tue, 28 Ap...

Web resources about - Re: MS Access and SAS datasets #4 - comp.soft-sys.sas

Data set - Wikipedia, the free encyclopedia
For IBM mainframe term for a file, see Data set (IBM mainframe) . For the telecommunications interface device, see Modem . A dataset (or data ...

Data : Where can I get large datasets open to the public?
Answer (1 of 91): Here's the ones I've found most useful: CrunchBase, US Census, Google Public Data, Infochimps, Timetric, Factual, Freebase, ...

YouTube - Hans Rosling: Let my dataset change your mindset
Hochgeladen am 31.08.2009 http://www.ted.com Talking at the US State Department this summer, Hans Rosling uses his fascinating data-bubble software ...

The Mindset, Skillset, Dataset Approach to Social Media
... Social media is comprised primarily of unstructured data, which is difficult to analyze. A new approach called Mindset, Skillset, Dataset can ...

Sending large datasets to Amazon? Use the Post Office
Amazon has introduced a new method to move large amounts of data to and from …

The Full Dataset on What VCs are Thinking About Funding in 2016
... challenging and many other startups were cutting costs (as many of ours has done in late 2015). We promised that we would clean up the dataset ...

Yahoo Releases the Largest-ever Machine Learning Dataset for Researchers
Yahoo is announcing the public release of the largest-ever machine learning dataset to the research community.

IDG Contributor Network: Are datasets truly anonymized? Two well-suited researchers are going to find ...
With little fanfare or formality, Adam Smith , associate professor of computer science and engineering in Penn State's School of Electrical Engineering ...

House GOP looks to shed light on EPA secret datasets
House Republicans have introduced a bill that would block the Environmental Protection Agency from crafting regulations based on “secret” scientific ...

Guest Contribution: “Capital Control Measures: A New Dataset”
Today we are pleased to present a guest contribution written by Andrés Fernández (IDB), Michael W. Klein (Tufts), Alessandro Rebucci (Johns Hopkins ...

Resources last updated: 3/18/2016 8:17:17 PM