Thanks Astounding. The above is very easy and does exactly what is needed. Paul ... View more

Hi Art That is exactly the stopping point and the issue. I guess I assumed Access was more capable than that. Thanks for the link also. The link gave me an idea though, which is to link tables in multiple Access DBs. I only have Access for the time being so linking may have to do. Paul ... View more

I was able to somewhat successfully run the export using the below Proc, however, about half way through the file, SAS stopped and printed the below error in the log file. I tried to load the second half of the file into a different table in the same DB starting with the records it stopped on and am getting an error for "Error attempting to CREATE a DBMS table. ERROR: Execute: Cannot open database ''. It may not be a database that your application recognizes, or the file may be corrupt..". When I look at the specific record that the export originally stopped on, it doesn't appear to be any different than others. The records up to the stopping point appear to have loaded successfully. The record set being exported is quite large, 7.3 GB. Has anyone run into this? Paul PROC EXPORT DATA=SASd.court_events             OUTTABLE="CourtEvents"             DBMS=ACCESS REPLACE;      DATABASE="F:\access.accdb"; RUN; 15         PROC EXPORT DATA=SASd.court_events 16                     OUTTABLE="CourtEvents" 17                     DBMS=ACCESS REPLACE; 18              DATABASE="F:\access.accdb"; 19         RUN; 1 The SAS System                                                      08:55 Monday, December 24, 2012 ERROR: Execute: Unable to insert row WARNING: File deletion failed for _IMEX_.CourtEvents.DATA. NOTE: PROCEDURE EXPORT used (Total process time):       real time           1:01:39.14       cpu time            1:01:26.30       ERROR: Export unsuccessful.  See SAS Log for details. NOTE: The SAS System stopped processing this step because of errors. 20         21         22         GOPTIONS NOACCESSIBLE; 23         %LET _CLIENTTASKLABEL=; 24         %LET _CLIENTPROJECTPATH=; 25         %LET _CLIENTPROJECTNAME=; 26         %LET _SASPROGRAMFILE=; 27         28         ;*';*";*/;quit;run; 29         ODS _ALL_ CLOSE; 30         31         32         QUIT; RUN; 33         ... View more

Hi Haikuo Thanks for the response and I have not used Hash () objects before and your code above is somewhat beyond where I am, but will work through it and post back. ... View more

Paige-I haven't changed problems mid-thread, I haven't gotten to the 50% issue yet. I was still working on getting the proc means to work. Once that is done, then I am going to look at what you indicated above and Hai's response actually. Reeza- I had asked a month or so ago about proc lifetest and its ability to calculate medians based on entire populations-missing or not. I don't know if this is what you mean. ... View more

Thanks Paige. I ran the below and did not get either the median or the quartiles in the output and am not getting an error either. I am getting the mean, st dev, min,. max, N. Paul proc means data=issuejoinedNNNAsort median q1 q3; var dur_filing_issuejoin; by cnty_name filingYear; output out=test11; run; ... View more

How do I output from PROC Means to a data set? There is no 'out' option. Paul ... View more

Also, in Enterprise Guide, there is a tab called 'Output Data' that appears when you run something (similar to the below). How do I export the contents of 'Output Data' to a data set? Paul proc lifetest data=issuejoinedNNNA;   ods select Quartiles;   ods output Quartiles=annual;   time dur_filing_issuejoin*censor_filing_issue(1);   strata cnty_name filingYear; run; Pau ... View more

I am using Enterprise Guide 5.1. Based on your response, what I would like to do is to save the output from lifetest using quartiles and from Proc Means in a data set. Neither of these two functions has an 'out' option. Does anyone know how to do this? Paul ... View more

Thanks Cynthia. That explains it then. ... View more

Hi I am trying to export to a MS Access 2010 DB using the below statement and am getting an error for "ERROR: FILE= or TABLE= is required and must be specified.". However, I do have a file name indicated. I was just going to create a new table within this DB for the data set, do I need to do something different? Paul proc export data=SASd.court_events dbms=access file="F:\MetricFiles\2013_Changes\metrics.accdb"; run; ... View more

I have been able to import other SAS files from this SAS program into Access, so it is not Access. With this particular file, I tried to eliminate columns to see if it was due to a data issue, but I got the same error regardless of which columns were in the file. I was not aware you could export directly into a DB. I only see file export options? Actually, I don't know if I have the SAS DB software to be able to do this actually. Paul ... View more