Campacting Memory Problem

[Trying_My_Hardest]

I am working with a very large Database and have likely reached Access
limitations but hopefully someone can remedy a problem.

I compacted a 1.3 Gb database, it failed and said that it was going to
expand my virtual memory and then my system completely ran out of memory. It
has now filled my C:\ and I can't seem to find the file that filling my
system.

Where do go to eliminate the source of the memory problem.

 

[Jerry Whittle]

First reboot your computer if you haven't done so.

Next using Windows Explorer go to the directory holding your database file
and make a copy of the mdb(s) files to another drive or maybe a DVD. If not
enough room, you might be able to zip up the database and copy it to a CD.
Nothing like a recent backup just in case.

Next look in that folder and see if there are any very large, unexplained
files. When doing a compact and repair, Access makes a copy of your database
with a different name. The last steps are delete the old, bloated database
file and to rename the new, hopefully smaller mdb file to the original name.
If you find some, delete them plus any old antique backup files. Might be a
good idea to move them to a safe place also.

While still in Windows Explorer right click on the C-drive icon and select
properties. How much free space do you have? You need at least 1.3 GB to do a
compress. You might even need more space to allow your virtual memory to
expand on the hard drive. If using Windows XP there should be a Disk Cleanup
button. Click it and maybe get rid of some junk. Speaking of which, it might
be time delete or move some files.

If your hard drive is pretty cluttered and you get rid of a lot of files, it
might be time to do a defragment also.

Now see if you can compact and repair the database.

 

[dbahooker]

MDB is friggin crap dont use it for anything ever

i mean.. aren't you tired of

compact/repair
refresh/relink
performance HELL-- especially across a NETWORK?

use MSDE or SQL express; MSDE is free duh!!

-aaron