f



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 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
afdbn (102)
5/24/2005 5:26:21 PM
comp.soft-sys.sas 142828 articles. 3 followers. Post Follow

0 Replies
434 Views

Similar Articles

[PageSpeed] 21

Reply:

Similar Artilces:

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: 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 #3
Jean - Unfortunately you are stuck - SAS only allows dataset names up to 32 bytes long - using name literals or conventional names. Defining short-named queries of your tables within MSAccess is a very good idea. The SAS libname engine will read the queries as tables and it doesn't necessitate changing your table names. Paul Choate DDS Data Extraction (916) 654-2160 -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of JKamgang@Yahoo.com Sent: Wednesday, January 16, 2008 9:32 AM To: SAS-L@LISTSERV.UGA.EDU Subject: How to access automatically in SAS a MS Access table name which has more than 32 characters? 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...

Re: Deleting SAS Data from a SAS DATASET #3
The disadvantages of using SQL delete are (1) NOBS= is no longer accurate, and (2) POINT= may behave unexpectedly. If those are not issues, then the delete would be faster, with or without an index, than recreating the data set (especially if the data set has indexes that would need to be rebuilt). -- Jack Hamilton jfh@alumni.stanford.org On Aug 15, 2008, at 11:17 am, Mary wrote: > One thing you might do is to add an index on the snap_dt to the > dataset; if that's there then you should be able to delete the > records in place: > > proc sql; > delete from prod.master_date; > where snap_dt = "&end_dt"d; > quit; > run; > > In both the ways you are trying now you are creating new data sets > rather than deleting records from the current data set; it would > seem to me that a SQL delete statement would be faster than creating > new datasets even if there isn't an index on the date. > > -Mary > ----- Original Message ----- > From: SUBSCRIBE SAS-L Chandra Gadde > To: SAS-L@LISTSERV.UGA.EDU > Sent: Friday, August 15, 2008 12:14 PM > Subject: Deleting SAS Data from a SAS DATASET > > > Hi All > > I have several SAS datasets that are very very big. (50GB of size). > Every > month, the data is being appended to these datasets. I need to > deleted the > data which is greater than 24 months. What is the best method to do > this? > Please help me. > ...

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: SAS and MS Access #3
DDE works. Here is an example: filename ecw dde "msaccess|ecw;view For Publication!all" lrecl=2000 notab; data ecw; infile ecw firstobs=2 dsd dlm='09'x missover; input country : $60. [etc.] ; [etc.] A serious problem arises if there are newlines within text fields. If they are not masked somehow, they are interpreted as end-of-record indicators, which makes a real mess of things.. If there are simple ways to mask newlines, in either direction (Access to SAS or SAS to Access), I don't know them. In the example above, I am reading a view which I created solely to drop the fields containing newlines (fortunately I did not need those fields on the SAS side). On Wed, 5 May 2004 23:33:43 -0400, Peter Hruby <hrubyp@SYMPATICO.CA> wrote: >Hi SAS-L, > >I am wondering what choice do I have to access tables in MS Access datbase. >Can I use SAS/Access to ODBC or SAS/Access to PC Files or DDE or WB scripts? >I appreciate any experience and examples. > >Thanks >Peter. ...

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 #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: 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 #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 #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 #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 #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: SAS Formats
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 labels only associate a textual label with a (numerical) value, that's all. And with (statistical) procedures both the value and its label may be printed. SAS formats can be viewed as some kind of transformation of (numerical and character) values, often intended for representation purposes (like value labels, but also quite often for conversion purposes. See the SAS docs, it's too extensive. With SAS PROCs generally only either unformatted values or formatted values are being displayed. Briefly, in SAS any numerical or character value, value range, value list or value range list can be assoc...

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: Storing SAS-programs and -macros in SAS-datasets on a HOST-platform #3
Hi. Howard is correct (no surprise). You can use the catalog access method on the FILENAME statement to write entries to a catalog, then use %INCLUDE to use the entries. There's a lot of info in the on-line help (using SAS on a PC)... FILENAME fileref CATALOG 'catalog' <catalog-options>; The CATALOG access method in the FILENAME statement enables you to reference a SAS catalog as an external file. You can then use any SAS commands, statements, or procedures that can access external files to access a SAS catalog. etc. Then, CPORT and CIMPORT can be used to exchange the...

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: MS Access
Thanks Joe! Your posts always offer good info and they help me learn a lot. I only tried the data step update because it was something I read about in one of the many helpful SAS papers out there. That explains the log 'replace' note versus an 'update' note. So, here's what I did. I made a little temp data set with 2 obs and 3 variables: State_Project_Number Report_Month Payment_Disburse 0005-05-101 06-2009 111111 0008-14-110 06-2009 111111 Next, used SQL (my SQL knowledge being very limited): PROC SQL; UPDATE RADS.MONTHLY_S...

Re: Import MS Access data to SAS #3
In v9 with PC Files Access there's my favorite - the libname engine. http://support.sas.com/onlinedoc/913/getDoc/en/acpcref.hlp/pclibname.htm libname mymdb "c:\demo.mdb"; proc sql; select idnum, lname from mymdb.staff where state='NY' order by lname; quit; hth Paul Choate DDS Data Extraction (916) 654-2160 > -----Original Message----- > From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Guibo > Xing > Sent: Friday, March 24, 2006 11:10 AM > To: SAS-L@LISTSERV.UGA.EDU > Subject: Import MS Access data to SAS > > Hi all, > > What is a good way to transfer MA Access data to SAS. I used proc import > (or > import wizard), but some data formats were lost. Thanks! ...

Re: How does SAS handle multiple sessions accessing a same dataset #3
Andre, you are right. To add for the "only real OS, zOS": libname xx "aaa" disp=shr; And you are also right: the FSP-modules FSEDIT and FSVIEW have a record locking mechanism. In FSVIEW you can say "modify record" for that, in FSEDIT it's default. However there is a problem on zOS (and some others which work similar): you cannot open a dataset in edit-mode which is in a library, you allocated with disp=shr. So there the only way is SAS/SHARE to use the record-locking. In hierarchical file-systems, there is chance to get it to run. However, if a program is merging something into a dataset or opened a dataset with SET, I don't think that anybody is able to read there. The logic, even if you write to the same dataset with: data a; merge a b; by xx; run; for A a dummy dataset is created, if the step is successful, the original a is deleted and the new one is renamed to a. A DB like DB2 is working "in place" if you insert any records to a table. If you update something, you must first delete the records, change them and insert them again. That allows a record locking mechanism which is necessary for online DBs. In SAS only SAS/SHARE adds that ability. So if you have online applications, which are to be updated concurrently or updated while reading should be allowed, you should use SHARE. Gerhard On Wed, 9 Apr 2008 09:45:03 +0200, Andre Wielki <wielki@INED.FR> wrote: >Stephen >about your point 2) >I remember...

Re: from SAS to MS Access without Proc Export #3
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 Hi, Bill, Consider producing .csv file on MF side, Then, later, move it to pc. MS Access should have no problem importing (or linking) .csv file into its table. Just my $.02 Cheers, Chang ...

Re: Exporting Multiple SAS files to MS Access #3
thanks so much Paul, worked great! ...

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 ...

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