Design Speed is SLOW

Can anyone give some hints or tips on designed in Access Forms for Access
2003? It appears that after every design change, the underlying query must
execute (this is my guess as to what is happening) before I can make another
change. This makes designing extremely slow if the query is a larger/slower
query. I can get around this by deleting the query name from the data source
property, then making all changes to the form, then re-added query name when
completed, but am wondering if there is anything else I can do to speed up
Form / Reports. I don't remember Access 2000 being like this.

Thanks for any advice!

Luke

When the form is NOT in design view, does the underlying query still take a
long time? If so, perhaps the underlying data would benefit from indexing
on any fields the query uses to sort, select or join...

Regards

Jeff Boyce
Microsoft Office/Access MVP


"Luke Bailey" wrote in message
...
Can anyone give some hints or tips on designed in Access Forms for Access
2003? It appears that after every design change, the underlying query
must
execute (this is my guess as to what is happening) before I can make
another
change. This makes designing extremely slow if the query is a
larger/slower
query. I can get around this by deleting the query name from the data
source
property, then making all changes to the form, then re-added query name
when
completed, but am wondering if there is anything else I can do to speed up
Form / Reports. I don't remember Access 2000 being like this.

Thanks for any advice!

Dear Luke:

If it isn't the query, itself, you might check to ensure that "Name
AutoCorrect" is disabled. And, it might be worth checking if you have an
"LBD" locking issue as described he

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

HTH
Fred Boer

"Luke Bailey" wrote in message
...
Can anyone give some hints or tips on designed in Access Forms for Access
2003? It appears that after every design change, the underlying query
must
execute (this is my guess as to what is happening) before I can make
another
change. This makes designing extremely slow if the query is a
larger/slower
query. I can get around this by deleting the query name from the data
source
property, then making all changes to the form, then re-added query name
when
completed, but am wondering if there is anything else I can do to speed up
Form / Reports. I don't remember Access 2000 being like this.

Thanks for any advice!

....No, I don't notice a slow response in general with a query. This is
really a question in general and not directly on a particular form. The
problem persists from database to database on all forms in design view. Some
are worse than others. It just seems that designing forms in 2003 is
Extremely slow compared to the previous version. There is a delay to move
from field to field, to make changes, etc. It appears that the query
executes after every change (moving from field to field, size changes, etc.).
I can change this by de-linking the query, then making the changes, then
re-linking the table or query, but wondering if there is anything else I can
do to speed up Access form design...

"Jeff Boyce" wrote:

Luke

When the form is NOT in design view, does the underlying query still take a
long time? If so, perhaps the underlying data would benefit from indexing
on any fields the query uses to sort, select or join...

Regards

Jeff Boyce
Microsoft Office/Access MVP


"Luke Bailey" wrote in message
...
Can anyone give some hints or tips on designed in Access Forms for Access
2003? It appears that after every design change, the underlying query
must
execute (this is my guess as to what is happening) before I can make
another
change. This makes designing extremely slow if the query is a
larger/slower
query. I can get around this by deleting the query name from the data
source
property, then making all changes to the form, then re-added query name
when
completed, but am wondering if there is anything else I can do to speed up
Form / Reports. I don't remember Access 2000 being like this.

Thanks for any advice!

I had already checked to make sure NAME Autocorrect is disabled. And it's
not the LDB locking issue described. I'm wondering if anyone can verify that
Access Forms in design view do in fact re-query whenever you move from one
ctrl to another or after changes are made. And if so (as this is what
appears to be happening), can this feature be turned off? Also, most of the
files I am working on are on Network folders. Anything particular on how
Access behaves when DB's are located on a network location? Should the files
be copied down to a local directory before working on in design view?

Thanks!


"Fred Boer" wrote:

Dear Luke:

If it isn't the query, itself, you might check to ensure that "Name
AutoCorrect" is disabled. And, it might be worth checking if you have an
"LBD" locking issue as described he

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

HTH
Fred Boer

"Luke Bailey" wrote in message
...
Can anyone give some hints or tips on designed in Access Forms for Access
2003? It appears that after every design change, the underlying query
must
execute (this is my guess as to what is happening) before I can make
another
change. This makes designing extremely slow if the query is a
larger/slower
query. I can get around this by deleting the query name from the data
source
property, then making all changes to the form, then re-added query name
when
completed, but am wondering if there is anything else I can do to speed up
Form / Reports. I don't remember Access 2000 being like this.

Thanks for any advice!

No. The form does not requery the records each time you change any property
of the form or controls in design view.

Well, if the form is based on a crosstab query it might. The solution there
would be to set the Column Headings property of the crosstab, so Access
knows what the fields are without having to run the query to completion.

Hopefully you have a split database, and you are working on a local (C:
drive) copy of the front end, so we are not talking about network lag on
design.

I strongly suggest you walk through each item in Tony Toews' FAQ. It is
definately worth the learning experience, and will probably identify the
cause of your issue. Also worth a compact, decompile, compact sequence.

If the slowness of the network itself is a contributing factor, you will
notice a significant delay when you open the Relationships window (Tools
menu.) This assumes there are several related tables in the back end, of
course. But that still should not make the form slow to work with once you
have it open in design view.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Luke Bailey" wrote in message
...
I had already checked to make sure NAME Autocorrect is disabled. And it's
not the LDB locking issue described. I'm wondering if anyone can verify
that
Access Forms in design view do in fact re-query whenever you move from one
ctrl to another or after changes are made. And if so (as this is what
appears to be happening), can this feature be turned off? Also, most of
the
files I am working on are on Network folders. Anything particular on how
Access behaves when DB's are located on a network location? Should the
files
be copied down to a local directory before working on in design view?

Thanks!


"Fred Boer" wrote:

Dear Luke:

If it isn't the query, itself, you might check to ensure that "Name
AutoCorrect" is disabled. And, it might be worth checking if you have an
"LBD" locking issue as described he

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

HTH
Fred Boer

"Luke Bailey" wrote in message
...
Can anyone give some hints or tips on designed in Access Forms for
Access
2003? It appears that after every design change, the underlying query
must
execute (this is my guess as to what is happening) before I can make
another
change. This makes designing extremely slow if the query is a
larger/slower
query. I can get around this by deleting the query name from the data
source
property, then making all changes to the form, then re-added query name
when
completed, but am wondering if there is anything else I can do to speed
up
Form / Reports. I don't remember Access 2000 being like this.

Thanks for any advice!