By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,392 Members | 1,561 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,392 IT Pros & Developers. It's quick & easy.

Growing database

P: n/a
Hi,

I am producing what I would have expected to be quite a small database. (By
small I mean in terms of the the code etc rather than the data.) I have had
all sorts of problems, as I'm a novice, with creating combo boxes and event
procedures, then deleting them etc. Has this somehow created a lot of
'empty space'. (Excuse the terminolgy!) If this is the case, is there any
way of retrieving it? So far I have used 'Compact and Repair' and made a
new databese and copied all the tables etc to it. All to little avail.

Thanks

John
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
John M wrote:
Hi,

I am producing what I would have expected to be quite a small database. (By
small I mean in terms of the the code etc rather than the data.) I have had
all sorts of problems, as I'm a novice, with creating combo boxes and event
procedures, then deleting them etc. Has this somehow created a lot of
'empty space'. (Excuse the terminolgy!) If this is the case, is there any
way of retrieving it? So far I have used 'Compact and Repair' and made a
new databese and copied all the tables etc to it. All to little avail.


During the design process, and especially when creating tables and using
queries, the database will inflate. All kinds of temporary data objects
are created.

When you Compact, these temporary objects are removed. Many queries will
take a moment extra the first time they run after a Compact (namely to
re-create the temporary object, which acts as speedup).

You don't need to Repair, and unless instructed to do so, shouldn't.

Creating a new database and importing objects from the other usually
solves any corruption issues, and tends to bring the size down.

So far, you followed 'the right path'. How many forms have you got?
Average number of controls?
Large tables? Are the tables in the same database, or did you link them?
(in the latter case, their content size should not add to the database
of course)

--
Bas Cost Budde
http://www.heuveltop.org/BasCB
but the domain is nl

Nov 12 '05 #2

P: n/a
Thanks for the reply - I've not got many forms - but two produce charts, and
I wonder if this could be the issue.
What did you mean by 'You don't need to Repair, and unless instructed to do
so, shouldn't'? There is only one option on the menu related to this ....
Compact and Repair!

Thanks in advance

"Bas Cost Budde" <ba*@heuveltop.org> wrote in message
news:c0**********@news2.solcon.nl...
John M wrote:
Hi,

I am producing what I would have expected to be quite a small database. (By small I mean in terms of the the code etc rather than the data.) I have had all sorts of problems, as I'm a novice, with creating combo boxes and event procedures, then deleting them etc. Has this somehow created a lot of
'empty space'. (Excuse the terminolgy!) If this is the case, is there any way of retrieving it? So far I have used 'Compact and Repair' and made a new databese and copied all the tables etc to it. All to little avail.


During the design process, and especially when creating tables and using
queries, the database will inflate. All kinds of temporary data objects
are created.

When you Compact, these temporary objects are removed. Many queries will
take a moment extra the first time they run after a Compact (namely to
re-create the temporary object, which acts as speedup).

You don't need to Repair, and unless instructed to do so, shouldn't.

Creating a new database and importing objects from the other usually
solves any corruption issues, and tends to bring the size down.

So far, you followed 'the right path'. How many forms have you got?
Average number of controls?
Large tables? Are the tables in the same database, or did you link them?
(in the latter case, their content size should not add to the database
of course)

--
Bas Cost Budde
http://www.heuveltop.org/BasCB
but the domain is nl

Nov 12 '05 #3

P: n/a
John M wrote:
Thanks for the reply - I've not got many forms - but two produce charts, and
I wonder if this could be the issue.
What did you mean by 'You don't need to Repair, and unless instructed to do
so, shouldn't'? There is only one option on the menu related to this ....
Compact and Repair!


Oh, that may be a version issue. I was speaking Access 97.

Graphical elements *can* cause database bloat. (nice search term)

But I can't get you out because I don't know where you're in.
--
Bas Cost Budde
http://www.heuveltop.org/BasCB
but the domain is nl

Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.