Well an MDE can't be created until all the code in the parent MDB is
compiled. Do you compile your code often? Have you ever tried a decompile,
recompile, followed by a Compact and Repair? 8mb for a FE without any tables
is HUGE. Sounds like the FE needs to be cleaned up. Any unused forms,
reports, and queries?
Once a query is run for the first time, Access optimizes it and even caches
the results. Try running something that goes slow then a few seconds run it
again to see what happens.
Name AutoCorrect really slows down forms and other things in the database.
Go to Tools, Options, General tab and turn off Name AutoCorrect. Possibly
creating an MDE updates everything in the parent MDB first.
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
"John Milbury-Steen" wrote:
[Quoted Text] > Hi Access gurus,
>
> I want to report an amazing and sudden speedup of my database, which I
> cannot explain.
> Split, front end and back end, about 8 MB each, in a2003, several
> clients some using a2000, some using a2003. (I know, mixed versions, a
> definite danger sign.) The front end is on each client's machine as an mdb
> file. (I know, it should be mde, and I am working on that.)
> For one a2000 user a particular form took 20 seconds.
> I create an a2000mde on his machine. No speed up.
> I run the old a2000mdb and the form now takes 1 sec!
>
> I conclude that some part of the process of creating an mde optimizes
> the mdb. How do you explain this?
>
>
>
>
|