Excel Front End Dashboard - Access Back End - 3 Million Rows of Data - Refresh Issues

So I have put together a dashboard in excel that relies on 4 tables of data in access.

One table is about 3 Million Rows.

The other 3 are about 300k each.

The dashboard went together without any issues as I built the pieces and integrated them into a single excel file. However I added a new month of data to the backend in access and now excel cannot refresh. I had no problems refreshing the dashboard prior to the new data.

Office 2010, Access 2010, (32bit).

Any idea what could be causing this issue? I have been watching the memory usage and it has yet to exceed 1.4gigs of memory which I have exceeded many times in the past with a previous version of the dashboard. Please advise if you have any ideas as to what may be causing this strange behavior.

The link references the query. When the query is updated in access i go to excel and download the new data. The link doesn't have anything to do with this. I think the problem is memory limitations. I was watching where excel bugs out and it is when it gets to about line 3.7M of out 3.75 Million. Watching the memory it is sitting around 1.6 gbs at this point and it likely doesnt have the memory available to play with the new data, while holding onto the old data. This is when it geives the error message about an error getting the data.

I've actually been researching this today. I began to break the file apart tab by tab and refreshing piece by piece and found that one of the queries was causing the problem. It would get up to about 1.7 gigs of memory when it would stop responding. People have tested excel's memory limitations before and they are actually triggered as low as 1.6 gigs even though the nominal limit is 2 gigs. Apparently excel requires continuous blocks of data so the 2 gig limitation in excel is probably being tripped without me seeing it. I have our purchaser ordering me 4 more gigs of ram and 64 bit version of excel so I can overcome this memory limitation. If this does not solve the issue I might be back but I am thinking hidden limitations are driving this erratic behavior.

I also found a crazy work around if anyone wants to try it---

Hitting refresh All breaks the memory limitation. However if you go into the connection itself between excel and access and just retarget the same table it goes through and manually refreshes the pivots 1x1. Seems to update just fine and work after.