f



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'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 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
nospam1405 (4666)
5/25/2005 1:25:48 AM
comp.soft-sys.sas 142828 articles. 3 followers. Post Follow

0 Replies
394 Views

Similar Articles

[PageSpeed] 4

Reply:

Similar Artilces:

Re: Deleting SAS Data from a SAS DATASET #5
I also read that this could be a problem on machines that have multiple = processors, such as running DB2; if the data is clustered and each = processor takes care of one cluster, then you could have queries all = hitting the same processor instead of distributing the load across all = processors, thus potentially slowing down queries in peak periods where = you have multiple queries at the same time, if queries tend to be based = on the month (such as bank statements). Thus I'd proceed with caution = on the idea of splitting one table into 24 tables with one view without = making sure the other consequences of doing so are fully understood. -Mary ----- Original Message -----=20 From: Mary=20 To: SAS-L@LISTSERV.UGA.EDU=20 Sent: Friday, August 15, 2008 4:09 PM Subject: Re: Re: Deleting SAS Data from a SAS DATASET A view helps on deletes, but I wonder how it affects performance of = querying the data- wouldn't storing the data in 24 different locations = cause a significant slowdown in perfomance upon querying the data versus = having it all in one table that is indexed? If this data is queryied a = lot but only deleted once a month, the time in querying (which probably = is in peak time) could be much more important than the time in deleting = (which could be run when the computer is not busy, such as nights or = weekends). =20 -Mary ...

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 #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 #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 #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: 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 #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 #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 >ta...

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
Karan, If you are running SAS interactively, you can view the files in the SAS explorer window if you first execute the statement Options nofmterr; This will allow you to open the file for viewing without having the format catalog. Daniel J. Nordlund Research and Data Analysis Washington State Department of Social and Health Services Olympia, WA 98504-5204 -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Karan Bhatia Sent: Tuesday, July 19, 2005 2:48 AM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: SAS Formats - converting SAS dataset into SPSS data 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 Groeneveld [mailto:jim1stat@YAHOO.CO.UK] Sent: Tuesday, July 19, 2005 2:29 PM To: SAS-L@LISTSERV.UGA.EDU; Karan Bhatia Subject: Re: SAS Formats - converting SAS dataset into SPSS data Hi Karan, SAS formats are more than SPSS value labels. In SPSS, as you may know, value lab...

Re: Converting from SAS 5 to SAS 9 #5
Mikeey I did try V8 before I sent the posting just to be sure that V5toV6 was not available and I too, found it not there. I see that Dale did not find it in a V6.12 installation. I just ran a mainframe 6.09E job and the proc is there. I find it odd that it would not be available in 6.12 since this is a V6 proc. The spelling is V5TOV6 Nat Michael Raithel <michaelraithel@W To: SAS-L@LISTSERV.UGA.EDU ESTAT.COM> cc: Sent by: "SAS(r) Subject: Re: Converting...

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: from SAS to MS Access without Proc Export #5
How about you cron (?) something like this job on the MF in batch mode: /*FTP LOCAL PC ASSUMING IIS FTP SERVER IS RUNNING.*/ filename abc ftp '' cd='/test/' user='ben.powell' host='HOST.IP' pass='XXXXXXXX'; data _NULL_; file abc dlm = ',' dsd; set &exportdataset; put VAR1 VAR2; run; Then use a scheduled task on the PC to suck the data in, a suitable interval after the ftp is completed. If unsure, you can run a %DO loop to check the record count and see if it is still being written to before getting SAS to trigger the Access Macro to import the data. CSV files have no limit. Hope that is of some interest, Ben. On Mon, 22 Nov 2004 15:03:59 -0500, Bill Droogendyk <bill_droogendyk@DOFASCO.CA> wrote: >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: 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: R vs. SAS (was Replacement for SAS (SPSS vs. SAS, redux)) #5
I think that SAS and R are very similar, even though their designs are very different. What matters is that both can be used to accomplish the same things - just as English and Swahilli serve the same purpose (communication) equally well. As for the copyleft "mess", do you really believe the propaganda and outright lies perpetrated by some companies? Remember, they want you to pay $$$ for your software, and copyleft poses a huge threat to that goal. -----Original Message----- From: Peter Flom [mailto:flom@NDRI.ORG] Sent: Thursday, February 05, 2004 12:57 PM To: SAS-L@LISTSERV.UGA....

Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. #5
Good deal Bob, atleast that company was headed in the right direction IMO... I have given such tests and taken them. I ussually give them a data set, the specs I want them to follow, and a example of what I want the output to look like. Then I tend to give them like 4 or 5 hours if they need it to complete the project. In reallity they should be done in an hour or so. The test should be challenging but not too challenging, and the solution should involve a few data steps, procedures, and some type of reporting..... 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: Bob_Abelson@HGSI.COM Reply-To: Bob_Abelson@HGSI.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 17:22:59 -0400 I interviewed at a company that gave a test where I had a half hour to produce a very simple report using PROC REPORT. I was provided all the manuals I wanted, but because I had used PROC REPORT before, I wanted none of them. I finished in five minutes, and most people on SAS-L would be able to beat that time. Bob Abelson HGSI 240 314 4400 x1374 bob_abelson@hgsi.com "toby dunn" <tobydunn@HOTMAIL.COM> Sent by: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> 09/04/2007 05:15 PM Please respond to "toby d...

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: 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: SAS/access for Oracle and MS SQL server are different license? #5
Dear SAS-L-ers, Power poster Ya Huang penned the following reply to my own posting: > > 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? > Ya, yes; you are right. You would have to license either one or the other of those SAS/Access products. I am sorry to read that you do not have them. Short of asking a SQL Server programmer/DBA to dump tables to a flat file, I do not have any ideas. Ya, best of luck with this bummer of a situation! I hope that this suggestion proves helpful now, and in the future! Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Michael A. Raithel "The man who wrote the book on performance" E-mail: MichaelRaithel@westat.com Author: Tuning SAS Applications in the MVS Environment Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172 Author: The Complete Guide to SAS Indexes http://www.sas.com/apps/pubscat/bookdetails.jsp?ca...

Re: SAS System Viewer 9.1 unable to open SAS datasets ( SAS 9.1.3)
A question in return: is your table from windows? compressed from another system? and specially with personnel formats hard coded inside? Andre msiddu2000 a �crit : > SAS System Viewer 9.1 was able to open datasets that were created by > V8 engine (SAS 8.2), but is unable to open datasets that are created > with V9 engine (SAS 9.1.3). > > Does this need SAS System Viewer to be upgraded ? > or > Something else needs to be done ? > > -- Andr� WIELKI INED (Institut National d'Etudes D�mographiques) Service Informatique 133 Boulevard Davout 75980 Paris Cedex 20 m�l : wielki@ined.fr t�l : 33 (0) 1 56 06 21 54 ...

Re: How to access automatically in SAS a MS Access table name
i am not sure if SAS will support long file name if you use libname. a workaround is to use passthrough. On Jan 16, 2008 12:31 PM, JKamgang@Yahoo.com <JBKamgang@gmail.com> wrote: > Dear All, > > > > Happy New Year , > > > > Please, I need your help in figuring out how to access in SAS a MS > Access > table name which has more than 32 characters. As this program merges 5 > databases, I need to have almost everything automated. That's why I > don't want to rename manually the table names. > > > > Please find the program below. > > > > Thanks in advance for your kind assistance, > > > > Jean Baptiste > > > > The program: > > - - - > > > > options VALIDVARNAME=ANY ; > > libname DBsource access 'S:\Data > Management\External\Projects\MTCT-Plus\MTCT-Plus November 2007 > Data\Programs\Data\MTCT-PlusData All.mdb'; > > /* Creating the Pediatric HIV result information additional */ > > > > data* pedResultadd ; > > set dbsource.'tblInfantHIVTestResultsAdditional'n (keep = > > testid studyid labid i2 i2_da i2_mo i2_yr i2a i2b i2text > > ); > * > > run*; > > - - - The log - - > > 1636 > > 1637 /* Creating the Pediatric HIV result information additional */ > > 1638 > > 1639 data pedResultadd ; > > 1640 set dbsource.'tblInfantHIVTestResultsAdditional...

Web resources about - Re: MS Access and SAS datasets #5 - 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:16:24 PM