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

Expanding DB

P: n/a
I have a FE BE Db for handling membership of various clubs. The Db is split
into a FE & BE, with all the active tables in the BE. The only tables in the
FE are pretty static (such things as paths to various files e.g. where the
front end is stored for each club and which fields to hide on forms
depending on which club is being used) The back end is about 9Mb, so there
is a lot in it.. Unless I do a compact on close, the file size seems to
increase rapidly. The "non standard" routines I use are Peter's
ShrinkerStretcher and also a routine to hide certain fields on forms if they
do not apply to a certain Club. Any ideas why it keeps growing

Thanks

Phil
Jan 8 '08 #1
Share this Question
Share on Google+
4 Replies


P: n/a
"Phil Stanton" <ph**@stantonfamily.co.ukwrote in message
news:13*************@corp.supernews.com...
>I have a FE BE Db for handling membership of various clubs. The Db is split
into a FE & BE, with all the active tables in the BE. The only tables in
the FE are pretty static (such things as paths to various files e.g. where
the front end is stored for each club and which fields to hide on forms
depending on which club is being used) The back end is about 9Mb, so there
is a lot in it.. Unless I do a compact on close, the file size seems to
increase rapidly. The "non standard" routines I use are Peter's
ShrinkerStretcher and also a routine to hide certain fields on forms if
they do not apply to a certain Club. Any ideas why it keeps growing
Images are sometimes responsible for file bloat, are you storing images?

Keith.
www.keithwilby.com

Jan 8 '08 #2

P: n/a
Thanks for replying

Yes, but only a non changing one in the company information table. This
table is frequently "read", but only "written" once in a blue moon

Phil

"Keith Wilby" <he**@there.comwrote in message
news:47********@glkas0286.greenlnk.net...
"Phil Stanton" <ph**@stantonfamily.co.ukwrote in message
news:13*************@corp.supernews.com...
>>I have a FE BE Db for handling membership of various clubs. The Db is
split into a FE & BE, with all the active tables in the BE. The only
tables in the FE are pretty static (such things as paths to various files
e.g. where the front end is stored for each club and which fields to hide
on forms depending on which club is being used) The back end is about 9Mb,
so there is a lot in it.. Unless I do a compact on close, the file size
seems to increase rapidly. The "non standard" routines I use are Peter's
ShrinkerStretcher and also a routine to hide certain fields on forms if
they do not apply to a certain Club. Any ideas why it keeps growing

Images are sometimes responsible for file bloat, are you storing images?

Keith.
www.keithwilby.com

Jan 8 '08 #3

P: n/a
"Phil Stanton" <ph**@stantonfamily.co.ukwrote in message
news:13*************@corp.supernews.com...
Thanks for replying

Yes, but only a non changing one in the company information table. This
table is frequently "read", but only "written" once in a blue moon
I may be wrong but I seem to remember reading somewhere that, when a table
with images is accessed bloat can occur. Like I say I may be wrong but I
think it's better practice to store links to images rather than the images
themselves.

Regards,
Keith.
www.keithwilby.com

Jan 9 '08 #4

P: n/a
I have a vague feeling you are right. I know OLE objects tend to be bad
news. Will give it a whorl

Thanks

Phil

"Keith Wilby" <he**@there.comwrote in message
news:47********@glkas0286.greenlnk.net...
"Phil Stanton" <ph**@stantonfamily.co.ukwrote in message
news:13*************@corp.supernews.com...
>Thanks for replying

Yes, but only a non changing one in the company information table. This
table is frequently "read", but only "written" once in a blue moon

I may be wrong but I seem to remember reading somewhere that, when a table
with images is accessed bloat can occur. Like I say I may be wrong but I
think it's better practice to store links to images rather than the images
themselves.

Regards,
Keith.
www.keithwilby.com

Jan 9 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.