You might also try a decompile, but are you storing images or other objects in the db? Earlier versions of Access didn't handle that very well, and the database would bloat far in excess of the size of the objects.
You might also try a decompile, but are you storing images or other objects in the db? Earlier versions of Access didn't handle that very well, and the database would bloat far in excess of the size of the objects.
No images or other. And most of the larger tables are stored on the backend. I think that I ran an overly large make table query one day, and if I could look at my tables by size I could easily find it.
For pure data to get it that large it would be millions of records. Offhand I don't know of a way to get table by table sizes in Access. It's not in MSysObjects.
For pure data to get it that large it would be millions of records. Offhand I don't know of a way to get table by table sizes in Access. It's not in MSysObjects.
This page has a script in post 7. Something of a kludge but effective none the less. I don't see any possibility of an alternative. It exports each table individually to a new database and reports the difference in filesize between that and and an empty database.