Time to move on...

PeterM wrote:
Actually, the 80 meg .mde is just the front end...we have our tables
out on a server provided by a host provider. The app has over 125
forms, 300 queries and about 45 tables.

You have something strange in your design. My main app has way more objects
than that and weighs in at a little over 20 MB on a fresh MDE. Do you have lots
of embedded images or something?

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

I've removed all graphics from the forms and reports which dropped it down
about 5 meg only.

Is there a way in Access to see if a query, form, report, macro and module
are referenced in the app? If I could determine the dead items, I could
reduce the size by deleting them?

Don't think I'm doing anything strange..........

"Rick Brandt" wrote:

PeterM wrote:
Actually, the 80 meg .mde is just the front end...we have our tables
out on a server provided by a host provider. The app has over 125
forms, 300 queries and about 45 tables.

You have something strange in your design. My main app has way more objects
than that and weighs in at a little over 20 MB on a fresh MDE. Do you have lots
of embedded images or something?

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Per PeterM:
Actually, the 80 meg .mde is just the front end...we have our tables out on a
server provided by a host provider. The app has over 125 forms, 300 queries
and about 45 tables.

That seems like a lot of megs.
I'm looking at one of my old apps right now that has:

--------------------------------
131 Forms
918 Queries
91 Reports
60,000+ lines of code
67 Links to back-end tables
51 Embedded model tables
168 Links to temp tables
--------------------------------

It's less than 30 megs (28.944 kb).

Are you on to the thing where you rename the app,
do a /Decompile on the command line, compile, then
compact the newly-compiled version into another
db that has the original name?
--
PeteCresswell

I'm not quite sure what you're asking. When I go to create an .mde, I open
the .mdb, goto Tools Database Utilities Make MDE File and choose an
existing .mde.

Do I need to be compiling something to create a .mde? I also distribute
this app as a .mdb where I go to the startup options and restrice access to
the database window, etc. Is there somehting I need to do to that .mdb?

"(PeteCresswell)" wrote:

Per PeterM:
Actually, the 80 meg .mde is just the front end...we have our tables out on a
server provided by a host provider. The app has over 125 forms, 300 queries
and about 45 tables.

That seems like a lot of megs.
I'm looking at one of my old apps right now that has:

--------------------------------
131 Forms
918 Queries
91 Reports
60,000+ lines of code
67 Links to back-end tables
51 Embedded model tables
168 Links to temp tables
--------------------------------

It's less than 30 megs (28.944 kb).

Are you on to the thing where you rename the app,
do a /Decompile on the command line, compile, then
compact the newly-compiled version into another
db that has the original name?
--
PeteCresswell

I created a copy of the .mdb and then deleted all forms, queries, reports,
macros, modules, etc so that the app is empty. It's now 19meg when it's
empty. I'm using Access 2002.

"(PeteCresswell)" wrote:

Per PeterM:
Actually, the 80 meg .mde is just the front end...we have our tables out on a
server provided by a host provider. The app has over 125 forms, 300 queries
and about 45 tables.

That seems like a lot of megs.
I'm looking at one of my old apps right now that has:

--------------------------------
131 Forms
918 Queries
91 Reports
60,000+ lines of code
67 Links to back-end tables
51 Embedded model tables
168 Links to temp tables
--------------------------------

It's less than 30 megs (28.944 kb).

Are you on to the thing where you rename the app,
do a /Decompile on the command line, compile, then
compact the newly-compiled version into another
db that has the original name?
--
PeteCresswell

Per PeterM:
I created a copy of the .mdb and then deleted all forms, queries, reports,
macros, modules, etc so that the app is empty. It's now 19meg when it's
empty. I'm using Access 2002.

That's the same version my app was running under.

Have you tried compacting?
--
PeteCresswell

I've discovered that the reports are the offenders. I only have 22 reports
and they don't appear to be anything strange. There is our company logo on
each of them and I'm hoping that will reduce the size.

When I made a copy of the .mdb and then deleted the reports, the file size
went from 68 meg to 38 meg.

Looks like I'm gonna have to create a separate .mdb with just the reports in
them and distribute that separately.

Unless you have any other ideas? Regardless, thank's for taking the time to
help!

"(PeteCresswell)" wrote:

Per PeterM:
I created a copy of the .mdb and then deleted all forms, queries, reports,
macros, modules, etc so that the app is empty. It's now 19meg when it's
empty. I'm using Access 2002.

That's the same version my app was running under.

Have you tried compacting?
--
PeteCresswell

Per PeterM:
There is our company logo on
each of them and I'm hoping that will reduce the size.

Been there. Can't remember the numbers, but it was amazing how much memory the
graphics eat up on MS Access reports.
--
PeteCresswell

(PeteCresswell) wrote in message
:
Per PeterM:
There is our company logo on
each of them and I'm hoping that will reduce the size.

Been there. Can't remember the numbers, but it was amazing how much memory
the graphics eat up on MS Access reports.

Would it help to use one small report for the logo, the use that as
subreport on all the others?

--
Roy-Vidar

Per PeterM:
Unless you have any other ideas?

David Epsom's post at the end of this thread is worth reading.

I thought I was pretty sophisticated in my deployment strategy.
After reading David's, I realize I'm still in the bush leagues.

The essence of his seems to be that he has broken up the app into separate
components (as you are thinking of doing), but linked them all into one 'master'
app.

--
PeteCresswell