form design is extremely slow

  • Thread starter Thread starter Christopher Glaeser
  • Start date Start date
C

Christopher Glaeser

A form is based on a query with many (15) fields. Placing fields from the
query onto the form is extremely slow. Selecting a field on the form,
dragging a field to a new location on the form, and similar operations can
take 10 to 15 seconds to redraw. Any ideas why this may be so slow?

Best,
Christopher
 
Are you talking about stand alone machine here, or is a network involved?

I would probably get rid track autoc correct, but not knowing any details
here, it is hard to guess what your problem could be.

What version...and is a network involved would *really* help my wild
guessing.

However, in the mean time, just work your way through the following
list....one of them will likely fix your problem:

http://www.granite.ab.ca/access/performancefaq.htm

Try the above list.....
 
Are you talking about stand alone machine here, or is a network involved?

Yes, the tables are on a network drive. Windows XP SP2 with Access 2003.
Why do the tables affect simply selecting or dragging a field in a form
design? Would you recommend importing the tables until the form design is
complete? It's so tediously slow, I don't think I can complete the form
design at this pace.

Best,
Christopher
 
Yes, the tables are on a network drive. Windows XP SP2 with Access 2003.
Why do the tables affect simply selecting or dragging a field in a form
design?
Click to expand...

Because you are on a network, and ms-access then opens, and checks the field
names of the table (and, gazillion other things) during design time.
(how could code compile that has a me.CompanyName if the field does not
exists in the table? ).

So, design time this will cause network traffic.
Would you recommend importing the tables until the form design is complete?
It's so tediously slow, I don't think I can complete the form design at
this pace
Click to expand...

No, if you read that article, the KEY solution to your problem is to try the
persistent connection trick. The huge "delay" in the time taken for
ms-access to "re-build" the connection to the back end database. So, what we
do is FORCE the connection to remain open at all time.

Try the following trick:

Open your front end. Now, open any table that is linked to the back end.
Now, minimize that table. Now, start your design mode session...notice how
the huge delay is gone?

Remember, that "same" delay will occur when your application runs, so, you
would do VERY WELL to ALWAYS startup a persistent connection in your startup
form/code......(or, at the very least open some form attached to the back
end table..and minimize it).

Try the above...post back so we can all learn if my suggestion was
useful...or something of no use at all!!

Good luck...and do read through that list of things to check...(the
persisting connection trick likely will fix this problem...)..
 
Open your front end. Now, open any table that is linked to the back end.
Now, minimize that table. Now, start your design mode session...notice how
the huge delay is gone?
Click to expand...

Thanks for the detailed explanation. I opened all the tables, plus the
query on which the form is based, and left all of them open. At first, I
thought the form designer was working faster. I placed a new field with
relative ease. However, I noticed that if I move a field left, then right,
then left, etc, it starts bogging down. Apparently, merely selecting a
field and moving the mouse on then off then on top of the field causes major
computations and caching that soon swamps my computer. It's a 3 GHz Pentium
4 with 1 GB RAM.

Best,
Christopher
 
Thanks for the detailed explanation. I opened all the tables

You don't have to open all tables. You just have to open ONE table...as long
as it is a linked table
to the back end, then you should be ok...
However, I noticed that if I move a field left, then right, then left,
etc, it starts bogging down.
Click to expand...

Have you turned off track autoname correct?

Have you worked you way though that list?

I find that a2003 works just great on a 600mhz old computer here..and
anything more is rather snappy.

You have something seriously wrong with your application, or your
setup...just not clear which right now....
 
Back
Top