I am using exactly this type of macro:   %MACRO EXPORT_TABLE(table, database, name); PROC EXPORT DATA = WORK.&table. OUTTABLE = "&name." DBMS = ACCESS REPLACE; DATABASE = &database.; RUN; %MEND; %EXPORT_TABLE(Somename, "path.mdb", Anothername); However, if the file already exists, SAS doesn't replace it, but makes the file bigger in size (number of rows/cols are preserved, but size of the file is higher). You can imagine how many problems this causes.   Is there any way, how to deal with this? I have tried NEWFILE = yes;, but it doesn't work with access databases.   Thank you ... View more

I have a table with 87 columns and 3,924,060 rows, which I am trying to export as MDB Access File with PROC EXPORT (DBMS = ACCESS REPLACE). The PROC EXPORT settings should be correct as the code works correctly with other tables, however, with this one, SAS stops with this error:   ERROR: Execute: Unable to insert row WARNING: File deletion failed for _IMEX_.MyDataTable.DATA. ERROR: Export unsuccessful. See SAS Log for details. The .mdb file produced is little more than 2gb in size, with exactly 2,621,000 rows. I can see that some variables, which are obviously integers, are exported as double. This can be the cause that file is larger than it should be.   Also, I don't see a reason why should have SAS problem with exporting big table into ACCESS.   I should note that I work with 32bit version of SAS 9.4, Windows 7, MS Office 2013. (Problem persists also with 64bit SAS).   So I have two questions:   * Can I force SAS to export variable into Access as Integer, not as double? * Why does SAS in some point stop exporting the data?   Thank you   ... View more