f



Re: SAS and MS Access

If you don't then you could perhaps consider bolting on your own JDBC
interface in Java? (JDBC is free SAS ACCESS to PC is not...)

On Thu, 6 May 2004 07:27:13 +0100, =?iso-8859-1?q?Ari=20Toikka?=
<toikkari@YAHOO.CO.UK> wrote:

>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 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.
>
>
>---------------------------------
>  Yahoo! Messenger - Communicate instantly..."Ping" your friends today!
Download Messenger Now
0
ben.powell1 (971)
5/6/2004 10:16:00 AM
comp.soft-sys.sas 142828 articles. 3 followers. Post Follow

0 Replies
496 Views

Similar Articles

[PageSpeed] 57

Reply:

Similar Artilces:

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

Re: How to access automatically in SAS a MS Access table name #2
Hi Jean, It looks like your problem is that you've got a quote in a table name: Additional'n=20 If it is possible to rename that table, that might work. =20 Also, if you use the import feature in SAS, it will write code for you = that you can save and put in a program- you might try that to see if it = can handle this kind of file name. I'd rename the table in Access, = though- a quote in a table name is likely to contiously cause you = problems. -Mary ----- Original Message -----=20 From: JKamgang@Yahoo.com=20 To: SAS-L@LISTSERV.UGA.EDU=20 Sent: Wednesday, January 16, 2008 11:31 AM 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=3DANY ; 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.'tblInfantHIVTest...

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: SAS -> MySQL without SAS/ACCESS
XML, OleDb driver for SAS (free), ODBC driver from SAS (free). SAS/Access is only required to get data from a source, not the other way around. Alan Alan Churchill Savian www.savian.net -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of RolandRB Sent: Friday, June 13, 2008 1:50 AM To: SAS-L@LISTSERV.UGA.EDU Subject: Q: SAS -> MySQL without SAS/ACCESS What is the easiest and neatest way to get a sas data set into MySQL without using SAS/ACCESS? I am hoping there are some useful URLs for this. ...

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 #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: 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: SAS and MS Access #2
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. Hi, Peter, If you have SAS/Access OLE DB, then it gives you more control. The following code shows that you can use an access table as if it is a sas dataset. If field name has embedded blanks, you can use something like, 'field name'n as the variable name. dbmax_text dataset option handles long text fields (>254 or >1000, I can't remember exactly) or memo field. HTH. Cheers, Chang libname myMdb oledb provider = "Microsoft.Jet.OLEDB.4.0" properties=('Data Source'='c:\my.mdb') preserve_tab_names=yes ; proc freq data=myMdb.myTable(dbmax_text=32767); tables myField/list missing; run; libname myMdb clear; ...

Re: Q: SAS -> MySQL without SAS/ACCESS
If the dataset is not huge, then converting the database table into a CSV file may be the way to go. MYSQL's own CSV read/write facility is extremely efficient (or was when I used it three years ago). On Fri, Jun 13, 2008 at 3:50 PM, RolandRB <rolandberry@hotmail.com> wrote: > What is the easiest and neatest way to get a sas data set into MySQL > without using SAS/ACCESS? I am hoping there are some useful URLs for > this. > ...

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: 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: 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 #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: How to access a MS SQL file in SAS?
Are you opening your .csv file with Excel? that would truncate the number of records. You may want to create a libname for the SQL table or use Proc SQL pass-through. You'll need the SAS Access for your database, such as SAS Access for Relational Databases to use ODBC. If you create a libname for the table you can read it directly in either a datastep or Proc Sql using SAS commands. If you use Proc SQL pass-through you will need to be aware of how Transact SQL works and you'll need an odbc connection. Example: Pass-through where yourdatasourcename, etc are the names of the database and tables, etc. that are relevant to your database and odbc connection. Proc SQL; connect to odbc (datasrc=yourdatasourcename user=yourdatasourceusername pasword=yourdatasourcepassword); create view yourviewname as select * from connection to odbc (select col1, col2, etc from yourtablename where.... etc); Libname method example from online help: libname mydblib odbc noprompt="uid=testuser;pwd=testpass;dsn=sqlservr;" Data mydata; set mydblib.tablename; more statements..... run; Dan Sharp >>> Mayukh Dass <dass@UGA.EDU> 06/18/04 07:56AM >>> Hi, I have a view with 200000 records that was created in MS SQL. I was trying to transfer the view to the SAS to do some analysis on it. I tried to convert the view to a .cvs file, but it is loading only 65535 records. Is there any way of doing this? Thank you in advance, M...

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 #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: Import MS Access data to SAS
Hi, If you have the SAS/Connect,PC File Formats,etc. licensing pieces, then you can map directly with ODBC,LIBNAME,etc. Then you can use SQL, SQL-passthrough, the datastep, procs, and most other SAS tools. In SAS v9+ you can also use the SAS/ACCESS and OLEDB goodies. Examples can be found in the SAS-L Archives: ODBC connectivity http://listserv.uga.edu/cgi-bin/wa?A2=ind0104A&L=sas-l&P=R19688 returning stuff from MSAccess, non-returning do stuff on MSAccess http://listserv.uga.edu/cgi-bin/wa?A2=ind0106A&L=sas-l&P=R1312 long libname http://listserv.uga.edu/cgi-bin/wa?A2=ind0012A&L=sas-l&P=R6427 short libname http://listserv.uga.edu/cgi-bin/wa?A2=ind0202D&L=sas-l&P=R29674 fetching MSAccess list of tables http://listserv.uga.edu/cgi-bin/wa?A2=ind0202A&L=sas-l&P=R22823 creating table,add/del variables, updating table http://listserv.uga.edu/cgi-bin/wa?A2=ind0206A&L=sas-l&P=R7354 deleting table http://listserv.uga.edu/cgi-bin/wa?A2=ind0409A&L=sas-l&P=R4613 appending table http://listserv.uga.edu/cgi-bin/wa?A2=ind0411A&L=sas-l&P=R1726 OLEDB connectivity http://listserv.uga.edu/cgi-bin/wa?A2=ind0203B&L=sas-l&P=R6841 http://listserv.uga.edu/cgi-bin/wa?A2=ind0603D&L=sas-l&P=R24245 Hope this is helpful. Mark Terjeson Senior Programmer Analyst, IM&R Russell Investment Group Russell Global Leaders in Multi-Manager Investing -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L...

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
Hit Send too fast. Forgot to mention that these are all licensed: ---SAS/ACCESS Interface to ORACLE ---SAS/ACCESS Interface to SYBASE ---SAS/ACCESS Interface to PC Files ---SAS/ACCESS Interface to ODBC ...

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/MS Experts: Pass Protecting Excel Sheet Created By SAS
On Fri, 26 Jan 2007 13:09:25 -0500, Gerry <gpauline@PACE.EDU> wrote: >SAS-Xperts: > > > >Is there a way password protect an excel file created by SAS ? Preferably as >part of the application's processing. Excel files themselves can be >password protected, but is there a way for SAS to engage this, or a third >party utility available ? > > > >We needed to do the same thing with PDF files, which I'm told will be a new >feature (password protecting) in v9.2. We found a utility that operates from >the command that will accomplish what we wa...

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

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

Local access and transport area - Wikipedia, the free encyclopedia
Local access and transport area (LATA) is a term used in U.S. telecommunications regulation. It represents a geographical area of the United ...

Facebook Expanding Access to Conversion Lift Measurement
Facebook launched conversion lift measurement in January 2015 with the goal of helping advertisers track conversions instead of clicks, and the ...

Planet OS Opens Access To Weather Data
... for software developers using weather data to power their apps, researchers and climate specialists enabling them to discover, access and build ...

Access your clipboard from any PC or Mac with 1Clipboard
1Clipboard is a free tool which enables sharing your clipboard contents with other PCs or Macs. The developer says that Android and iOS apps ...

Ankara court bans Facebook and Twitter access - Business Insider
Turkey last year blocked access to Twitter over the sharing of photographs of a prosecutor being held at gunpoint by far-left militants.

US says losing access to China-claimed waters would be huge
CANBERRA, Australia (AP) — A U.S. Navy commander warned Wednesday that if the United States lost access to international waters claimed by China ...

MIT, Harvard researchers push new way for users to control access to personal data
Cryptography researchers at MIT and Harvard have developed software called Sieve that is designed to help users keep track of encrypted personal ...

How to access Google Drive files faster with Launch Center Pro
... Launch Center Pro has solved many workflow problems for me over the years. Most recently it’s been an immense time-saver when it comes to accessing ...

Cal Investigation Finds Assistant Coach Sexually Harassed Reporter Who Accused Him Of Trying To Trade ...
... a copy of Cal’s investigation into the matter, and even Hufnagel’s own statements make it appear that he attempted to trade sex for access, ...

Paragon's early access starts now, no more progress wipes
Paragon is gearing up for launch in the future, but for now, Epic is keen on putting it into an Early Access phase. The good news is that there ...

Resources last updated: 3/19/2016 3:24:03 AM