Question Delete table doesn't delete table!!!

[Knildon]

Hello again,
Not sure where this should be posted since I believe it involves more than just tables.
I have a DB with a large table (750k+records) that is built from 5 other tables. I update this table once a week by deleting the existing table and building a new table.
The problem I have is that when I delete the existing table, the name is removed from table list but the table contents appear to remain in the database. I can see this because the database size grows after each deletion instead remaining close to the same size.
Any idea how to prevent this problem??
I know that a repair and compress cures it but I would like to "nip it in the bud".
Thanks for any and all help.
Don
Still learning, but a little slower today!!!

 

[John Big Booty]

I don't believe there is any avoiding having to Compact and Repair when you delete tables.

From this link;

...

As you add and update data and change its design, a database file becomes larger. Some of this growth comes from new data, but some comes from other sources:

Access creates temporary, hidden objects to accomplish various tasks. Sometimes, these temporary objects remain in your database after Access no longer needs them.
When you delete a database object, the disk space that the object occupied is not automatically reclaimed — the database file still uses that disk space, even though the object is deleted.

As your database file fills up with the remains of temporary and deleted objects, its performance can degrade. Objects may open more slowly, queries may take longer than normal to run, and typical operations generally seem to take longer.

Note Compacting does not compress your data — it makes your database file smaller by eliminating unused space.

...

 

[Knildon]

Hi John,
Thanks for the quick response. I was afraid that might be the answer I get! Not that it's a huge problem but it extends the time used to build the new table.
My database is not split since it only has one user table and is only used by one person at a time. Would a split database make a difference?
If not, I'll have to figure out how to do the compact process using VBA.
Thanks again,
Don

 

[John Big Booty]

This article might answer some of those questions.