problems compacting a database

Topic

New Reply

I have a database (db) that was 56 000 k and when I win zipped i. it compressed to 5 200 K

I then generated two local tables that expanded the database to 950 000 K. I fear that the Db could top 2 G.

I deleted all the lines of these two tables using delete queries then compressed (compacted) the db, but I still got the same size of 950 000 K, and when zipped the win zip size was reduced to on 56 000 K. This size is far too large. What can I do to get the db to a smaller size.

Richard

Reply | Quote

Replies

The first thing to try is to create a new empty database, and then import everything but the two local tables into it – that should get you back to the original size. I presume this is an MDB file, but if the format is 2002/2003 there have been some reported issues with compact not being effective in some cases. Your post suggests that most tables are linked either in another MDB or linked via ODBC. If that is the case, that is either a large front-end database, or you are having issues compacting it prior to the local table generation. I have a front-end DB that has 300 tables (mostly linked), 300 queries, 150 forms and 200 reports with several large modules, and several large embedded graphics in reports that is about that size. If you have that complexity, fine, but if not then it sounds like there are compaction issues.

Reply | Quote

l have 240 attached tables via odbc -sql server and 6 local tables, some 200 queries and a hundred reports and forms. I did what you suggested and it worked (57 000 K).

Reply | Quote