Originally Posted by
Bat Dude
As a side note I installed MS Office 2010 64-bit version however, none of the internal VBA code developed would work in the 64-bit Access so I had to uninstall and re-install the 32-bit version of Office.
Probably you did not need to do that. There is a fix for this, but I think it's premature to get into it before you solve your size issue. Do report back on what happened after doing a compact/repair. AFAIK, whether a table contains many, many characters per field (as if it were csv data) or if they're separate records, the effect on the table/db size would be the same, notwithstanding any overhead resulting from complex designs, huge defined relationships, etc. Hopefully, you are not also storing objects/images in your tables.
You also cannot 100% believe what windows reports as a file size, believe it or not. Sometimes, a file is spread over so many drive sectors that the file occupies more space than it would if the drive was defragged. This usually isn't the case with network drives though.
Last edited by Micron; 07-23-2017 at 04:41 PM.
Reason: clarification
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.