 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / General 2 / June 2007Slow Startup - Usual Suspects Already Tried
Hello - I have a front end database that is about 55MB. It takes between 10 and 45 seconds to open initially depending on the computer. There is a startup form specified but the delay occurs before a single line of codes is executed. I have tried decompile (nice size decrease), turning off autocorrect and turning off subdatasheets in the back end. Auto virus on or off makes seems to make no difference. I'm using Access 2003 SP 2 but the db is in Access 2000 format. I'm not too sure what to try next. Any ideas? >Hello - I have a front end database that is about 55MB. It takes >between 10 and 45 seconds to open initially depending on the [quoted text clipped - 7 lines] > >I'm not too sure what to try next. Any ideas? If you have decompiled, you should then Compact and Repair, open the VBA editor and select Debug... Compile <project>, and compact again (otherwise it must recompile code when you open). See Tony's tips at http://www.granite.ab.ca/access for other suggestions. John W. Vinson [MVP] Thanks John! I did try those exact steps following the info at Tony's site already. No improvement in startup speed though. Is the FE local? If not, make a local copy and try again. Make a copy without the startup form. (also check for an autoexec macro), and try again: Does that take as long to open? If so, it is the Anti-virus. Check that again, more carefully. (david) > Hello - I have a front end database that is about 55MB. It takes > between 10 and 45 seconds to open initially depending on the [quoted text clipped - 7 lines] > > I'm not too sure what to try next. Any ideas? > Is the FE local? If not, make a local > copy and try again. [quoted text clipped - 22 lines] > > - Show quoted text - I've tried all those I'm afraid... Yes - FE is local. With or without startup form makes no difference (the delay seems to occurs before startup form opens) There's no autoexec macro Delay is still present (10 - 15 seconds on my current computer and longer on other ones) Anti-Virus is off. In addition: CPU is maxed during the delay period. I deleted all linked tables - no diff. Compile on demand setting makes no difference. From a different database, ow long does Application.dbengine.OpenDatabase( ... ) take? Or from vbs, after creating a dbe instance, dbe.OpenDatabase( ... ) If you rename the file extension, does that make any difference? If you load the file into wordpad, does that take just as long? This to try to separate out the file system effects of 'open' on the file. When you open, do you open Exclusive, or Shared? Does it make any difference? Note that lots of things happen before a form becomes visible: The form compiles if necessary, everything in the database and all libraries compile if necessary, all subforms load, and then all required data is loaded from tables -- before the form becomes visible. Broken table links and Broken mapped drives slow everything down before the first form is visible. Also check your Windows event viewer to see if there are any unexplained errors, and your Windows services to see if there are any services you should stop. >> Is the FE local? If not, make a local >> copy and try again. [quoted text clipped - 38 lines] > CPU is maxed during the delay period. I deleted all linked tables - no > diff. Compile on demand setting makes no difference. >Hello - I have a front end database that is about 55MB. It takes >between 10 and 45 seconds to open initially depending on the [quoted text clipped - 3 lines] >subdatasheets in the back end. Auto virus on or off makes seems to >make no difference. From your other replies you've certainly done reading on this topic. I was convinced decompile would've solved it but once you stated "nice size decrease" I knew you had done the decompile properly. Have you tried importing into a new MDB? Tony  SignatureTony 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/ > >Hello - I have a front end database that is about 55MB. It takes > >between 10 and 45 seconds to open initially depending on the [quoted text clipped - 17 lines] > Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm > Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/ Yup - tried that. I imported first the tables and queriesand start up time was normal. After I brought in the forms (and there are a few hundred) the delay was back. Should I just be chalking this up as expected behaviour? > I imported first the tables and queriesand start up > time was normal. After I brought in the forms (and there are a few > hundred) the delay was back. Should I just be chalking this up as > expected behaviour? In your first message you refer to "turning off autocorrect". I just want to verify that you turned off Name AutoCorrect (Tools -> Options..., General tab), not the "spelling Autocorrect" options that are listed under the Tools -> Autocorrect Options... dialog. If you've imported into a new database, make sure that Name AutoCorrect is off in the new database, too. SignatureDirk Goldgar, MS Access MVP www.datagnostics.com (please reply to the newsgroup) > Innews:1182370928.039011.280500@j4g2000prf.googlegroups.com, > [quoted text clipped - 14 lines] > > (please reply to the newsgroup) Thanks - name autocorrect is definitely the one I had turned off already. Good point on the setting prior to import - I will double check that one. > >Hello - I have a front end database that is about 55MB. It takes > >between 10 and 45 seconds to open initially depending on the [quoted text clipped - 17 lines] > Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm > Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/ This is somewhat a rhetoric question, but maybe if I wrote a function that would import forms (or heck, maybe all objects) one at a time and measure the length of time to do the import I may infact find there is a problem form? >This is somewhat a rhetoric question, but maybe if I wrote a function >that would import forms (or heck, maybe all objects) one at a time and >measure the length of time to do the import I may infact find there is >a problem form? Or try importing roughly a quarter of the objects at a time and see if there is a drastic slow down somewhere. How big is the MDB? Tony SignatureTony 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/ Per Kelsy: >I'm not too sure what to try next. Any ideas? I know you said the delay proceeded any form opens... but do you have any graphics on any forms? If so, it would only take a few minutes to clone a copy of the app, remove the graphics, and see if the problem goes away. I would do this myself if only because I don't know what goes on "under the hood" when MS Access starts up... SignaturePeteCresswell > Per Kelsy: > [quoted text clipped - 10 lines] > -- > PeteCresswell Yes - a few of the forms do have graphics. I'll try anything. I'll report back and later and let you know how it goes. I was doing the trick where you name a .bmp the same name as the access db (to replace the startup graphic), but I already tried it with the file renamed and no diff. Durn. I was going to say virus checker but you already tried it. For your linked tables are you using mapped drives or UNCs? UNCs can be slower. Also how far down the tree is the folder holding the BE? If they are many, many folders down, that can slow things down. Try moving the BE closer to root and see what happens. What happens if you move the BE to your computer? If much faster, that could be an indication of a network problem. SignatureJerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. > Hello - I have a front end database that is about 55MB. It takes > between 10 and 45 seconds to open initially depending on the [quoted text clipped - 7 lines] > > I'm not too sure what to try next. Any ideas? > For your linked tables are you using mapped drives or UNCs? UNCs > can be slower. This is not true. SignatureDavid W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ > Durn. I was going to say virus checker but you already tried it. > [quoted text clipped - 24 lines] > > - Show quoted text - I completed de-linked that back end and the problem still exists. The front end (where my problem is) is on a local drive 3 or 4 folders down. All folder names are relatively short. Not that I think this is relevent, but note that a folder can map to a different drive. And it is normally a good idea to have "Bypass traverse checking" privilege, (which is the default) (david) >> Durn. I was going to say virus checker but you already tried it. >> [quoted text clipped - 25 lines] > front end (where my problem is) is on a local drive 3 or 4 folders > down. All folder names are relatively short. > Hello - I have a front end database that is about 55MB. It takes > between 10 and 45 seconds to open initially depending on the [quoted text clipped - 7 lines] > > I'm not too sure what to try next. Any ideas? Kelsy, When you say front end database that is 55MB, that gives me pause. I assume that this is a non-split database, then. Have you tried splitting a copy of the database into BE/FE versions and then seeing what the FE start-up time is? Sincerely, Chris O. > > Hello - I have a front end database that is about 55MB. It takes > > between 10 and 45 seconds to open initially depending on the [quoted text clipped - 20 lines] > > Chris O. If your db really is split already, then I am curious why the FE has reached 55MB. Sincerely, Chris O. On Jun 21, 2:25 am, "Chris2" <rainofsteel.NOTVA...@GETRIDOF.luminousrain.com> wrote: > > > Hello - I have a front end database that is about 55MB. It takes > > > between 10 and 45 seconds to open initially depending on the [quoted text clipped - 28 lines] > > - Show quoted text - Absolutely has been split - this is just the FE. There are some local tables just for temporary storage, but that's it. Here's some stats during import. This is from a year ago and I have no idea what the options (eg. Name AutoCorrect) were during import: original size (after compact) 88,842,240 after queries imported 4,259,840 after tables 8,433,664 after modules 11,259,904 after macros 11,276,288 after forms 20,713,472 after reports 26,120,192 after menus and specs 26,583,040 after final compact 40MB (not a typo - size increased after compact) There's has been lots of good input here all and I have a bunch of things to try and check. I hope to have a solid session of debugging this later tonight. Unfortunately if I don't get to it this evening you won't hear back from me till towards the end of next week but I will definitely keep on it! > On Jun 21, 2:25 am, "Chris2" > <rainofsteel.NOTVA...@GETRIDOF.luminousrain.com> wrote: [quoted text clipped - 54 lines] > you won't hear back from me till towards the end of next week but I > will definitely keep on it! Kelsy, I can think of very little else. 1) Try running the Jet Compact Utility on a copy of the db. 2) Try pressing SHIFT during startup to see if any start-up related code is bypassed. (Is there: an AutoExec macro, code in the Open event, command line arguments in the box for that in Options?) 3) On a copy of the db, try a more "thorough" decompile for getting rid of Name Autocorrect corruption (I believe I copied this from a post by Allen Browne). 1. Uncheck the boxes under: Tools | Options | General | Name AutoCorrect Explanation of why: http://allenbrowne.com/bug-03.html 2. Compact the database to get rid of this junk: Tools | Database Utilities | Compact 3. Close Access. Make a backup copy of the file. Decompile the database by entering something like this at the command prompt while Access is not running. It is all one line, and include the quotes: "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile "c:\MyPath\MyDatabase.mdb" 4. Open Access, and compact again. 5. Open a code window. Choose References from the Tools menu. Uncheck any references you do not need. For a list of the ones you typically need in your version of Access, see: http://allenbrowne.com/ser-38.html 6. Still in the code window, choose Compile from the Debug menu. Fix any errors, and repeat until it compiles okay. Sincerely, Chris O. > 2) Try pressing SHIFT during startup to see if any start-up > related code is bypassed. (Is there: an AutoExec macro, code in > the Open event, command line arguments in the box for that in > Options?) A couple of suggestions that Chris's point #2 reminds me of: 1. are you using any calls to remote systems that might be unavailable? I just discovered a slowdown in some code that checks of a list of databases are accessible via the File System Object's FileExists/FolderExists functions, and it was hanging the startup of one form because the timeout on a system that wasn't on was very long. 2. try downloading the SysInternals FileMon program and have it capture what happens during startup of your app. This might point out some missing file that is timing out on you. SignatureDavid W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ > Hello - I have a front end database that is about 55MB. It takes > between 10 and 45 seconds to open initially depending on the [quoted text clipped - 7 lines] > > I'm not too sure what to try next. Any ideas? Another thought occurs to me: check your references. Are there any marked a missing? Any unusual ones? Maybe Access is trying to locate some referenced library, or reconcile different versions. SignatureDirk Goldgar, MS Access MVP www.datagnostics.com (please reply to the newsgroup) uh I'd reccomend moving to a database SERVER with a future Accsss MDB is crap and it always has been >> Hello - I have a front end database that is about 55MB. It takes >> between 10 and 45 seconds to open initially depending on the [quoted text clipped - 11 lines] > marked a missing? Any unusual ones? Maybe Access is trying to locate > some referenced library, or reconcile different versions. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.