Front End .mdb load time after update   

I have a front end that I have made at least 25 advanced updates to.  While 
working on my latest update,  I copied a form named Carrier and pasted it 
with the new name of CarrierEdit.  There was already a form named CarrierEdit 
and I told it to replace the current form.  When I did this access crashed 
and restarted.  This cause a corruption that told me "The module not found".  
I have since compacted and repaired, decompiled, recompiled, and compacted 
and repaired.  I have also copied all objects to a new blank database.  When 
I copied into the new database I was able to access all my objects, however, 
it runs so slow that its painfull.  I dont know what else to do, so any help 
would be great.!

date: Fri, 28 Sep 2007 12:56:01 -0700   author:   Ryan Tisserand

Re: Front End .mdb load time after update   

Ryan Tisserand  wrote:

>When 
>I copied into the new database I was able to access all my objects, however, 
>it runs so slow that its painfull.  

The three most common performance problems in Access 2000 or newer
are:
  - LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
  - sub datasheet Name property set to [Auto] should be [None]
  - Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Tony

-- 
Tony Toews, Microsoft Access MVP
   Please respond only in the newsgroups so that others can 
read the entire thread of messages.
   Microsoft Access Links, Hints, Tips & Accounting Systems at 
http://www.granite.ab.ca/accsmstr.htm
   Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

date: Fri, 28 Sep 2007 16:26:53 -0600   author:   Tony Toews [MVP]

Re: Front End .mdb load time after update   

Well, it was my backend database.  I moved all objects to a new, blank 
database and everything seems to be working now.

"Tony Toews [MVP]" wrote:

> Ryan Tisserand  wrote:
> 
> >When 
> >I copied into the new database I was able to access all my objects, however, 
> >it runs so slow that its painfull.  
> 
> The three most common performance problems in Access 2000 or newer
> are:
>   - LDB locking which a persistent recordset connection or an always
> open bound form corrects (multiple users)
>   - sub datasheet Name property set to [Auto] should be [None]
>   - Track name AutoCorrect should be off
> 
> If the problem is for everyone when starting up the MDB then it likely
> needs a decompile.
> 
> For more information on these, less likely causes, other tips and
> links to MS KB articles visit my Access Performance FAQ page at
> http://www.granite.ab.ca/access/performancefaq.htm
> 
> Tony
> 
> -- 
> Tony Toews, Microsoft Access MVP
>    Please respond only in the newsgroups so that others can 
> read the entire thread of messages.
>    Microsoft Access Links, Hints, Tips & Accounting Systems at 
> http://www.granite.ab.ca/accsmstr.htm
>    Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>

date: Tue, 2 Oct 2007 08:00:00 -0700   author:   Ryan Tisserand

Re: Front End .mdb load time after update   

Ryan Tisserand  wrote:

>Well, it was my backend database.  I moved all objects to a new, blank 
>database and everything seems to be working now.

Interesting that.  Thanks for posting back your solution.

Tony
-- 
Tony Toews, Microsoft Access MVP
   Please respond only in the newsgroups so that others can 
read the entire thread of messages.
   Microsoft Access Links, Hints, Tips & Accounting Systems at 
http://www.granite.ab.ca/accsmstr.htm
   Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

date: Sat, 06 Oct 2007 18:23:27 -0600   author:   Tony Toews [MVP]