Prev: ERROR: DBMS type EXCEL not valid for export????
Next: Convert Excel file created with tagsets.excelxp to xls/xlsx
From: Joe Matise on 26 Oct 2009 15:03 Do you have SAS/ACCESS for PC Files licensed? [PROC SETINIT; RUN; ] -Joe On Mon, Oct 26, 2009 at 1:37 PM, Carol Thurman <erbcjt(a)langate.gsu.edu>wrote: > Hi All, > > Why do I keep getting the error message below when I try to export data to > excel? > > Carol > > > >>>> PROC EXPORT DATA= WORK.HSPAL > >>>> OUTFILE= "J:\PAL 2009\High School Reliability.xls" > >>>> DBMS=EXCEL REPLACE; > > > > >>>>>ERROR: DBMS type EXCEL not valid for export. >
From: Joe Matise on 26 Oct 2009 15:10 Exporting to Excel directly through PROC EXPORT dbms=EXCEL is an extra license, yes (I presume due to using Microsoft technology?). Run the code: PROC SETINIT; RUN; and it will list the modules you have licensed. You can output data to excel in a few other ways if you don't have a license for PCFILES, though. I think DBMS=XLS might work, and if it doesn't, then you can look at either: * CSV and then open it in excel and save as... * ODS TAGSETS.EXCELXP * Another intermediary output destination that is readable by excel -Joe On Mon, Oct 26, 2009 at 2:06 PM, Carol Thurman <erbcjt(a)langate.gsu.edu>wrote: > I'm not sure, Joe. We just purchased this license from SAS a few months > ago - I just thought it came with it. Is this an add-on that we will have > to purchase? > > Carol > > >>> Joe Matise <snoopy369(a)gmail.com> 10/26/09 3:03 PM >>> > Do you have SAS/ACCESS for PC Files licensed? > [PROC SETINIT; RUN; ] > -Joe > > On Mon, Oct 26, 2009 at 1:37 PM, Carol Thurman <erbcjt(a)langate.gsu.edu > >wrote: > > > Hi All, > > > > Why do I keep getting the error message below when I try to export data > to > > excel? > > > > Carol > > > > > > >>>> PROC EXPORT DATA= WORK.HSPAL > > >>>> OUTFILE= "J:\PAL 2009\High School Reliability.xls" > > >>>> DBMS=EXCEL REPLACE; > > > > > > > > >>>>>ERROR: DBMS type EXCEL not valid for export. > > > >
From: Savian on 26 Oct 2009 22:14 On Oct 26, 1:10 pm, snoopy...(a)GMAIL.COM (Joe Matise) wrote: > Exporting to Excel directly through PROC EXPORT dbms=EXCEL is an extra > license, yes (I presume due to using Microsoft technology?). Run the code: > PROC SETINIT; RUN; and it will list the modules you have licensed. > > You can output data to excel in a few other ways if you don't have a license > for PCFILES, though. I think DBMS=XLS might work, and if it doesn't, then > you can look at either: > * CSV and then open it in excel and save as... > * ODS TAGSETS.EXCELXP > * Another intermediary output destination that is readable by excel > > -Joe > > On Mon, Oct 26, 2009 at 2:06 PM, Carol Thurman <erb...(a)langate.gsu.edu>wrote: > > > > > I'm not sure, Joe. We just purchased this license from SAS a few months > > ago - I just thought it came with it. Is this an add-on that we will have > > to purchase? > > > Carol > > > >>> Joe Matise <snoopy...(a)gmail.com> 10/26/09 3:03 PM >>> > > Do you have SAS/ACCESS for PC Files licensed? > > [PROC SETINIT; RUN; ] > > -Joe > > > On Mon, Oct 26, 2009 at 1:37 PM, Carol Thurman <erb...(a)langate.gsu.edu > > >wrote: > > > > Hi All, > > > > Why do I keep getting the error message below when I try to export data > > to > > > excel? > > > > Carol > > > > >>>> PROC EXPORT DATA= WORK.HSPAL > > > >>>> OUTFILE= "J:\PAL 2009\High School Reliability.xls" > > > >>>> DBMS=EXCEL REPLACE; > > > > >>>>>ERROR: DBMS type EXCEL not valid for export.- Hide quoted text - > > - Show quoted text - I doubt if there are any licensing restrictions due to Microsoft. The Excel file format is open source and has been for awhile. Alan http://www.savian.net
From: Joe Matise on 28 Oct 2009 09:41 I was thinking more along the lines of using the JET/ACE engines, which are Microsoft products; there could be licensing fees associated with that. -Joe On Mon, Oct 26, 2009 at 9:14 PM, Savian <savian.net(a)gmail.com> wrote: > On Oct 26, 1:10 pm, snoopy...(a)GMAIL.COM (Joe Matise) wrote: > > Exporting to Excel directly through PROC EXPORT dbms=EXCEL is an extra > > license, yes (I presume due to using Microsoft technology?). Run the > code: > > PROC SETINIT; RUN; and it will list the modules you have licensed. > > > > You can output data to excel in a few other ways if you don't have a > license > > for PCFILES, though. I think DBMS=XLS might work, and if it doesn't, > then > > you can look at either: > > * CSV and then open it in excel and save as... > > * ODS TAGSETS.EXCELXP > > * Another intermediary output destination that is readable by excel > > > > -Joe > > > > On Mon, Oct 26, 2009 at 2:06 PM, Carol Thurman <erb...(a)langate.gsu.edu > >wrote: > > > > > > > > > I'm not sure, Joe. We just purchased this license from SAS a few > months > > > ago - I just thought it came with it. Is this an add-on that we will > have > > > to purchase? > > > > > Carol > > > > > >>> Joe Matise <snoopy...(a)gmail.com> 10/26/09 3:03 PM >>> > > > Do you have SAS/ACCESS for PC Files licensed? > > > [PROC SETINIT; RUN; ] > > > -Joe > > > > > On Mon, Oct 26, 2009 at 1:37 PM, Carol Thurman <erb...(a)langate.gsu.edu > > > >wrote: > > > > > > Hi All, > > > > > > Why do I keep getting the error message below when I try to export > data > > > to > > > > excel? > > > > > > Carol > > > > > > >>>> PROC EXPORT DATA= WORK.HSPAL > > > > >>>> OUTFILE= "J:\PAL 2009\High School Reliability.xls" > > > > >>>> DBMS=EXCEL REPLACE; > > > > > > >>>>>ERROR: DBMS type EXCEL not valid for export.- Hide quoted text - > > > > - Show quoted text - > > I doubt if there are any licensing restrictions due to Microsoft. The > Excel file format is open source and has been for awhile. > > Alan > http://www.savian.net >
From: Savian on 28 Oct 2009 21:01
On Oct 28, 7:41 am, snoopy...(a)GMAIL.COM (Joe Matise) wrote: > I was thinking more along the lines of using the JET/ACE engines, which are > Microsoft products; there could be licensing fees associated with that. > > -Joe > > > > On Mon, Oct 26, 2009 at 9:14 PM, Savian <savian....(a)gmail.com> wrote: > > On Oct 26, 1:10 pm, snoopy...(a)GMAIL.COM (Joe Matise) wrote: > > > Exporting to Excel directly through PROC EXPORT dbms=EXCEL is an extra > > > license, yes (I presume due to using Microsoft technology?). Run the > > code: > > > PROC SETINIT; RUN; and it will list the modules you have licensed. > > > > You can output data to excel in a few other ways if you don't have a > > license > > > for PCFILES, though. I think DBMS=XLS might work, and if it doesn't, > > then > > > you can look at either: > > > * CSV and then open it in excel and save as... > > > * ODS TAGSETS.EXCELXP > > > * Another intermediary output destination that is readable by excel > > > > -Joe > > > > On Mon, Oct 26, 2009 at 2:06 PM, Carol Thurman <erb...(a)langate.gsu.edu > > >wrote: > > > > > I'm not sure, Joe. We just purchased this license from SAS a few > > months > > > > ago - I just thought it came with it. Is this an add-on that we will > > have > > > > to purchase? > > > > > Carol > > > > > >>> Joe Matise <snoopy...(a)gmail.com> 10/26/09 3:03 PM >>> > > > > Do you have SAS/ACCESS for PC Files licensed? > > > > [PROC SETINIT; RUN; ] > > > > -Joe > > > > > On Mon, Oct 26, 2009 at 1:37 PM, Carol Thurman <erb...(a)langate.gsu.edu > > > > >wrote: > > > > > > Hi All, > > > > > > Why do I keep getting the error message below when I try to export > > data > > > > to > > > > > excel? > > > > > > Carol > > > > > > >>>> PROC EXPORT DATA= WORK.HSPAL > > > > > >>>> OUTFILE= "J:\PAL 2009\High School Reliability.xls" > > > > > >>>> DBMS=EXCEL REPLACE; > > > > > > >>>>>ERROR: DBMS type EXCEL not valid for export.- Hide quoted text - > > > > - Show quoted text - > > > I doubt if there are any licensing restrictions due to Microsoft. The > > Excel file format is open source and has been for awhile. > > > Alan > >http://www.savian.net- Hide quoted text - > > - Show quoted text - I don't think it works that way and my reasoning is that SAS can export on Unix as well as PCs. I doubt if JET runs on Unix. Alan |