http://msmvps.com/blogs/access/archive/2009/05/08/exceeding-2-gb-mdb-file-size-and-a-bit-of-tgif-humour.aspxExceeding the 2 Gb MDB file size gives you an exceedingly misleading error message: In Jet 4.0 one message that is received when the 2 Gb file size is exceeded is invalid argument. This is, of course, utterly confusing and can mean other things such asenCommunityServer 2008.5 SP2 (Build: 40407.4157)http://msmvps.com/blogs/access/archive/2009/05/08/exceeding-2-gb-mdb-file-size-and-a-bit-of-tgif-humour.aspx#1714769Mon, 10 Aug 2009 21:47:47 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1714769Sean NIcholas<p>I run across them all of the time. &nbsp;The error I have seen is &#39;Invalid Arguement&#39; when they are built via code.</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1714769" width="1" height="1">http://msmvps.com/blogs/access/archive/2009/05/08/exceeding-2-gb-mdb-file-size-and-a-bit-of-tgif-humour.aspx#1696712Thu, 25 Jun 2009 13:28:21 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1696712Charles Coleman<p>I&#39;ve only encountered one Access database &quot;in the wild&quot; that had exceeded 2 GB, and, while I can&#39;t recall what error messages it was giving, I think they were different from this. Basically there is no telling what Access may say is wrong, was my impression, if you let this happen The messages really made no sense...after scratching my head for a while, it occurred to me to look at the file size. </p> <p>The users were importing big recordsets daily from an Oracle database, and never deleting them or archiving them. After a couple of years of this, they had 2GB of data.</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1696712" width="1" height="1">