One option would be to separate it into multiple database files and linking
to them in your front-end. Move some of the tables to other files.
Another option is to upgrade to a newer version where you can double the
size.
Of course, repairing and compacting will help.
If you have a large number of reports, queries, and forms, you should be
split. Those objects should live in a front-end database which is linked to
the tables in a back-end database. If the majority of your 1gig is data,
then this may not help much.
Examine your structure. Is there redundant information? Customer name and
address in more than one record for example? Make sure your fiel is
normalized.
Is there old data that can be moved to an archive file?
Hope those ideas help, or get you started in the right direction.
In addition to Rick's useful suggestions, I thought I'd mention one other
thing, even though it may not apply:
Are you storing images in your database? Storing images in a database file
can cause it to grow tremendously. There are approaches to dealing with
images with Access that avoid this problem...
HTH
Fred Boer
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
