quick question about filesize

[martinmike2]

Hello,

I have a database front-end that has recently jumped from a lowely 3mb
to over 50mb. Is there anything normal that can cause this to
happen? The file in question contains only forms, reports, and
queries. All of the tables are split between 3 seperate back-ends,
for security purposes, with the FE linked to them. I have already
scrubbed the FE for redundant and unneded forms, reports, queries, and
code.

 

[Dale Fye]

Have you compacted the database?
--
HTH
Dale

Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.

 

[martinmike2]

Dale,

Its 50+mb after I compact, lol

 

[John Spencer]

Did you make any changes to the database application?

Did you add any pictures to the database application? Pictures can bloat the
application fairly quickly.

Did you try decompile, compact, compile, compact? Make a backup first.

See Allen Browne's site for recovering from corruption. Your database is
probably not corrupted, but following the steps for decompile, compact,
compile, compact should get the database down to minimum size.
http://allenbrowne.com/ser-47.html

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

 

[Tom van Stiphout]

On Mon, 25 Aug 2008 05:01:50 -0700 (PDT), martinmike2

You may have redundant compilations in your project. Compact,
/decompile, and Compact again.
Another option is to export all objects to text files and import them
again, using SaveAsText, LoadFromText.

-Tom.
Microsoft Access MVP

 

[martinmike2]

we have pictures stored in a seperate folder and only the path to them
stored in the database, not the actual picture. as far as
decompiling, I am on a company computer that is completely locked out,
even mtyping cmd in "RUN" dosnt bring up the command prompt, lol.

 

[Dale Fye]

I've got similar problems, but I get around it by creating a txt file with a
..BAT extension. Then I've got one line of code that decomplies my
application.

"C:\Program Files\Microsoft Office\Office12\ MSACCESS.EXE"
"C:\Work\MyApp.mdb" /decompile

Watch the word wrap.

--
HTH
Dale

Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.

 

[martinmike2]

Tried that Dale,

It opened the file then I compacted, no change.

 

[martinmike2]

even tried JetComp, no change.

having a moderate amount of sub queries and subforms wouldnt cause
this issue would it?

 

[Dale Fye]

No, most of my large databases (where I have split the front and back ends)
only result in 3-4 Meg front ends (and that is with lots of forms, queries
and reports). Generally, the front ends are much smaller than that.

Have you tried creating a new db, then importing all of the objects from the
old one into the new one? If you do this, make sure you don't forget to
import any of the
import specs or menus you have created in the old db.

Is there a chance you imported a table rather than linking to it?


--
HTH
Dale

Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.

 

[martinmike2]

i imported all the forms/queries/reports/modules into a new db file
and left the tables out. This resulted in a 198mb file that I
compacted, resulting in a 43mb file, so, not much difference.

 

[martinmike2]

I can email the files to you, with dummy data, if you want to look at
it, maybe you will see something I dont.

 

[John W. Vinson]

i imported all the forms/queries/reports/modules into a new db file
and left the tables out. This resulted in a 198mb file that I
compacted, resulting in a 43mb file, so, not much difference.

43Mb is a very reasonable size for a frontend. Many of mine are much larger.

One possible source of bloat - do you have any pictures, either in tables or
on forms? Access handles picture data very inefficiently.

 

[martinmike2]

i have a few forms and reports with embedded word documents, Tom
caught it last night.

 

[Larry Linson]

even tried JetComp, no change.

having a moderate amount of sub queries and subforms wouldnt cause
this issue would it?

Activities that create temporary workspace / workfiles can cause bloating in
the Front End. One such activity is executing certain queries (but it's
really difficult for those of us in The Great Access Unwashed to determine
details). The temporary workspace / workfiles, like other deleted records
and objects aren't recovered until a Compact and Repair (mantra: Compact and
Repair is my friend).

Larry Linson
Microsoft Office Access MVP

 

[John W. Vinson]

Activities that create temporary workspace / workfiles can cause bloating in
the Front End. One such activity is executing certain queries (but it's
really difficult for those of us in The Great Access Unwashed to determine
details). The temporary workspace / workfiles, like other deleted records
and objects aren't recovered until a Compact and Repair (mantra: Compact and
Repair is my friend).

.... and current backups are my REALLY REALLY GOOD friend!

 

[Larry Linson]

... and current backups are my REALLY REALLY GOOD friend!

Amen.

Larry Linson
Microsoft Office Access MVP