Avoiding MDE/ADE save-on-exit

[Atlas]

Once upon a time,
I was told that, even if at runtime, when exiting an MDE/ADE "application"
the MDE/ADE file is saved by access.

This could explain why my users, after a while (weeks), experience very slow
startup; once a new "release" is given, slowness disappeares; it appears
again after a while users load/unload the MDE/ADE.

As it is well known that while developing, garbage is stored into the
MDB/ADP files, giving slowness in the medium term, I thought that even at
runtime the beheviour could occur.

If that is the case there should be a way to prevent MDE/ADE saving them
selfs...........


Any hint?

 

[Darrin]

Have you tried going into the options and compacting/repairing on exit? That
should fix the issue.

 

[Atlas]

Have you tried going into the options and compacting/repairing on exit?
That
should fix the issue.

I'll go deeper to explain what's happening.

Usually, while developing, MDB/ADP size increases, leading into slow
startup. After decompiling/compacting and repairing, size shrinks down and
startup flyes.

Now back to my case.

When releasing to "production" a new MDE/ADE, I always pass through a
decompile/compact/repair process, to be sure and users get the smallest and
fastest "application".

Now the (maybe) problem

When users get a fresh copy of a MDE/ADE file, the startup is fast. After
weeks of using the same MDE/ADE file, startup gets slower and slower.

As it is well known that MDE/ADE are saved everytime Access exits, I thought
this could lead in the long term to slowness.

Any thoughts?

 

[Darrin]

That was my one thought on it because there are a lot of the folks I talk to
that don't know about that little trick. Sorry I could not help any further.