Front end grows when saving

[Hank]

Since learning from this group about decompiling around three
years ago, I use the decompile, and compact on a daily basis. (Yes, I
back it up first) When the code is released, it is now running at about
25 MB. For the past couple of months, when I make a small change in
the code and save it, the code expands from 25 MB to 70, 100, or even
as much as 150 MB.
Of course, decompiling and compacting still brings it back down to
25 MB but I wonder what is causing the huge growth. I'm using Access
2000.
Thanks,
Hank Reed

[Tom van Stiphout]

On 29 Aug 2005 04:59:22 -0700, "Hank" <ha********@aol.com> wrote:

Don't use the /decompile switch unless you have a really good reason.
File size does not count. See
http://www.trigeminal.com/usenet/usenet004.asp?1033

-Tom.

Since learning from this group about decompiling around three
years ago, I use the decompile, and compact on a daily basis. (Yes, I
back it up first) When the code is released, it is now running at about
25 MB. For the past couple of months, when I make a small change in
the code and save it, the code expands from 25 MB to 70, 100, or even
as much as 150 MB.
Of course, decompiling and compacting still brings it back down to
25 MB but I wonder what is causing the huge growth. I'm using Access
2000.
Thanks,
Hank Reed

[Ken Ismert]

Hank,

I decompile frequently, and have experienced no problems related to it.
Some observations:

* Extreme file size growth after small changes is a symptom, I my
experience, of very old databases with lots of objects that have been
continouosly modified over a long period of time. Try importing all the
objects into a blank, new database.

* 25MB is kind of large for a front end, in my opinion. You should
think about making it smaller, either by breaking it up into smaller
logical sub-applications, or offloading support code into DLLs using
Visual Basic.

* File size can indeed count, depending on how you update your
front-end on your user's computers.

-Ken

[David W. Fenton]

Tom van Stiphout <no*************@cox.net> wrote in
news:lt********************************@4ax.com:

Don't use the /decompile switch unless you have a really good
reason.

I disagree. I use it on a daily basis, and before distributing an
app for production use.

I have never lost a single line of code that wasn't already
corrupted to begin with.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Tim Marshall]

David W. Fenton wrote:

Tom van Stiphout <no*************@cox.net> wrote in
news:lt********************************@4ax.com:

Don't use the /decompile switch unless you have a really good
reason.

I disagree. I use it on a daily basis, and before distributing an
app for production use.

I have never lost a single line of code that wasn't already
corrupted to begin with.

I personally have found it helps greatly with Access 2003 file front end
sizes. My mdbs bloat terrifically in A2003 in development and I find
the general file size to be humoungous compared to what A97 provided me.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me

[David W. Fenton]

Tim Marshall <TI****@PurplePandaChasers.Moertherium> wrote in
news:de**********@coranto.ucs.mun.ca:

David W. Fenton wrote:

Tom van Stiphout <no*************@cox.net> wrote in
news:lt********************************@4ax.com:

Don't use the /decompile switch unless you have a really good
reason.

I disagree. I use it on a daily basis, and before distributing an
app for production use.

I have never lost a single line of code that wasn't already
corrupted to begin with.

I personally have found it helps greatly with Access 2003 file
front end sizes. My mdbs bloat terrifically in A2003 in
development and I find the general file size to be humoungous
compared to what A97 provided me.

I wonder if you have COMPILE ON DEMAND still turned on? THat's the
worst contributor to code bloat, seems to me, and should always be
OFF.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Tim Marshall]

David W. Fenton wrote:

I wonder if you have COMPILE ON DEMAND still turned on? THat's the
worst contributor to code bloat, seems to me, and should always be
OFF.

Arrgh, thanks for reminding me, no, I hadn't followed your previous
advice.

Question, though. Help says CoD "Determines whether a project is fully
compiled before it starts, or whether code is compiled as needed,
allowing the application to start sooner." Is there any trade off for
turning CoD off?

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

[David W. Fenton]

Tim Marshall <TI****@PurplePandaChasers.Moertherium> wrote in
news:df**********@coranto.ucs.mun.ca:

David W. Fenton wrote:

I wonder if you have COMPILE ON DEMAND still turned on? THat's
the worst contributor to code bloat, seems to me, and should
always be OFF.

Arrgh, thanks for reminding me, no, I hadn't followed your
previous advice.

Question, though. Help says CoD "Determines whether a project is
fully compiled before it starts, or whether code is compiled as
needed, allowing the application to start sooner." Is there any
trade off for turning CoD off?

No, seems to me. It's only for people who never compile their code.

Since any production database will go into use precompiled or as an
MDE in the first place, it's not an issue except during development.
Turning it off means you control when the code compiles (though if
you open an uncompiled form, it will compile as it needs to).

It's something that MichKa recommended long ago and I find that
turning it off it greatly improves reliability.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc