Results 1 to 3 of 3
  1. #1
    Star Lounger
    Join Date
    Sep 2001
    Location
    Pleasanton, California, USA
    Posts
    58
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Unresponsive front end (Acc2002)

    What would make a front end unresponsive. I copied and renamed a front end to make modifications. Now it is almost totally unresponsive - from 3sec to open a form, to a minute or more. Plus it is slow even moving around the database window - several seconds for a click to register. What could do this? I have compressed/repaired several times. I have imported all objects to a new database. I have checked VB references (and some are missing from the old version - like it doesn't list Microsoft Forms 2.0 Object Library in the new version, but does in the old version - and is nowhere on the list.). Any ideas?

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Unresponsive front end (Acc2002)

    I assume this is related to your question in <post#=253390>post 253390</post#>, right? When you create a new database and import objects, the new database does NOT inherit references. You have to set those yourself. If you had references set to files that are not in the default list (such as when you set a reference to another mdb file), then it will not show up in the list of the new database and you have to browse to find it in order to set the reference. There is no earthly reason for Access to show MS Forms in the list, since Access uses a different set of form and control objects than the rest of Office does. The only reason you would see MS Forms in the list is if you had set a reference to it, and you would have to do that by browsing for it.

    There are plenty of reasons why a front end could become slow in AXP. If you have Name Autocorrect turned on, it will slow things down significantly. If you have subdatasheets set to [Auto] in your tables (front OR back end), that can have a major impact. If you are linking to an Access 97 back end, that will slow things down tremendously too. In A2k and later, saved queries are optimized while SELECT statements and SQL built in code are not, so there is quite a noticeable delay the first time the query is run in a session, because Jet is optimizing the query. The next time you open the form in the same session, there should be no noticeable delay.

    If you provide more specifics, we might be able to help you figure it out. The business about the database window being slow suggests that either you have subdatasheets turned on or a *lot* of SELECT statement lookups in your tables or your backend is either in A97 or on a server, or both.
    Charlotte

  3. #3
    Star Lounger
    Join Date
    Sep 2001
    Location
    Pleasanton, California, USA
    Posts
    58
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Unresponsive front end (Acc2002)

    Thanks Charlotte. It was the name autocorrect. I had turned it on a few days ago because we were going to do some changes and I thought I would try it out. It didn't seem slow at first, but yesterday it was excruciating. I turned it off and the DB works fast again. Amazing.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •