Delayed Response Time

[Guest]

I am running WIN XP PRO and Office 2003 on a Pentium 4 with 512 RAM
In ACCESS, when I work design view for forms and reports, I have a 5-10
second delay from the time I take one action before I can take another.
Also, reports are slow to open.

I have used "compact and repair", but that does not correct problem.

Any help appreciated.

 

[Tony Toews]

I am running WIN XP PRO and Office 2003 on a Pentium 4 with 512 RAM
In ACCESS, when I work design view for forms and reports, I have a 5-10
second delay from the time I take one action before I can take another.
Also, reports are slow to open.

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

 

[Guest]

This sounds very much like the problem I am having with Access 2003. I have a
number of front end Access applications referencing a SqlServer database. A
very common task on this sort of application has been to bind a form to a
pass through query. This is no longer possible ... Access 2003 just wont
perform in form design view when bound to a pass through query. The delay
between attempting to make a change on the form and anything actually
happening is so long that it is impossible to design the form. However this
only seems to be a problem for MDB files. ADP files dont seem to have the
same problem ... the only difference I can see is the data binding ..one ODBC
and one OLEDB ... this hasnt been a problem with previous versions of Access
.... I am now actively looking for an alternative to Access as the changes
made in 2003, for example the ridiculous sandbox mode, in my opinion, are a
major backwards step. I would still appreciate a resolution of this problem
if anyone can help ..but it does look like goddbye Access ..a good rapid
development tool absolutely ruined !
--
PEDETENTIM "Step by Step"

I am running WIN XP PRO and Office 2003 on a Pentium 4 with 512 RAM
In ACCESS, when I work design view for forms and reports, I have a 5-10
second delay from the time I take one action before I can take another.
Also, reports are slow to open.

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

 

[aaron.kempf]

the biggest problem with using Access is this:

A) MDB is obsolete; has always been obsolete; and it will never be
unobsoleted.
B) move all your stuff to MSDE or SQL Server.
C) ADP can still use a lot of your forms and reports from MDB solution.

MSDE is _FREEEEEEEE_ for most practical purposes.

good luck

 

[aaron.kempf]

sandbox is a MAJOR step backwards

those crackheads at microsoft need to wake up to reality.

obviously a bunch of excel dorks is in charge of Access.

-Aaron

 

[Guest]

I am running WIN XP PRO and Office 2003 on a Pentium 4 with 512 RAM
In ACCESS, when I work design view for forms and reports, I have a 5-10
second delay from the time I take one action before I can take another.
Also, reports are slow to open.

I have used "compact and repair", but that does not correct problem.

Any help appreciated.

 

[Guest]

I am running WIN XP PRO and Office 2003 on a Pentium 4 with 512 RAM
In ACCESS, when I work design view for forms and reports, I have a 5-10
second delay from the time I take one action before I can take another.
Also, reports are slow to open.

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

 

[Guest]

Thank you for your response. I must say that you are above me in
understanding this issue.

I am running WIN XP PRO and Office 2003 on a Pentium 4 with 512 RAM
In ACCESS, when I work design view for forms and reports, I have a 5-10
second delay from the time I take one action before I can take another.
Also, reports are slow to open.

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

 

[Guest]

I hope that we can find a fix.

This sounds very much like the problem I am having with Access 2003. I have a
number of front end Access applications referencing a SqlServer database. A
very common task on this sort of application has been to bind a form to a
pass through query. This is no longer possible ... Access 2003 just wont
perform in form design view when bound to a pass through query. The delay
between attempting to make a change on the form and anything actually
happening is so long that it is impossible to design the form. However this
only seems to be a problem for MDB files. ADP files dont seem to have the
same problem ... the only difference I can see is the data binding ..one ODBC
and one OLEDB ... this hasnt been a problem with previous versions of Access
... I am now actively looking for an alternative to Access as the changes
made in 2003, for example the ridiculous sandbox mode, in my opinion, are a
major backwards step. I would still appreciate a resolution of this problem
if anyone can help ..but it does look like goddbye Access ..a good rapid
development tool absolutely ruined !
--
PEDETENTIM "Step by Step"

I am running WIN XP PRO and Office 2003 on a Pentium 4 with 512 RAM
In ACCESS, when I work design view for forms and reports, I have a 5-10
second delay from the time I take one action before I can take another.
Also, reports are slow to open.

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

 

[Guest]

I Think I am Lost, But I Appreciate allm the feedback

 

[Guest]

Thanks for comments. Strangely, I do not have the delay problem running same
version of ACCESS on my laptop. I tried to follow Tony's recommendations,
but without benefit. I may not have done them correctly.

Regardless, this is an unbearable situation.

 

[Guest]

This is a problem with the data binding // I am almost 100% sure.
Have you tried bibding the same form in an ADP project ? I think you will
find your problem does not transfer to ADP.
I am currently trying to replicate the problem on a clean machine .. I
suspect there is something wqrong with the MDAC rolled out with Access 2003.
I have confirmed the problem does not occur with Access 2002. My solution at
the moment is to develop with Access 2002 on a separate box. This is ok but I
do need to find the solution. Let me know if you find solution before I do.

 

[Tony Toews]

the biggest problem with using Access is this:

A) MDB is obsolete; has always been obsolete; and it will never be
unobsoleted.
Wrong.

B) move all your stuff to MSDE or SQL Server.

For various reasons sure. But so far nothing in your responses
indicates any good reasons to move.

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 Toews]

Thank you for your response. I must say that you are above me in
understanding this issue.

Thanks. But I've been working with Access for over ten years and
have surely read over 100K postings.

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

 

[Guest]

Ive been having a great time trying to replicate this problem and thought
maybe if I posted some results someone else might have a brainwave !
First, and in the context of binding to a pass through query, the problem
seems to be related to the complexity of the query. The delay is still there
with a simple "select field from table" but is much less evident.
Secondly, the form itself is designed relatively quickly .. but does not
appear for a long time (presumably because it is trying to map the data)
Third, any attempt to make design changes to the form fail because of the
delays noted previously.
Fourth, this problem is not present in Access 2002 or with Access Project.
I have been able to replicate on 3 clean machines, each with a fresh build
of Access 2003.
I intend to try an earlier MDAC to see if the problem still persists
...unfortunately work keeps getting in the way and I havent yet had time.
Finally, I am using a complex pass through query against SqlServer 2000
which runs efficiently returning data over the network with impressive
results.
I have also used the same query but as a stored procedure, binding the form
to the stored procedure using a pass through query (i.e. exec sProcTest) this
results in the same problem.
Im having fun trying ..but maybe someone already has a fix for this problem
in Access 2003.

 

[Tony Toews]

Thanks for comments. Strangely, I do not have the delay problem running same
version of ACCESS on my laptop.

However is the laptop using a local copy of the back end or is the
backend on the network?

I tried to follow Tony's recommendations,
but without benefit. I may not have done them correctly.

The simplest thing to start with is to open up a bound form and leave
it open. See if that helps with performance.

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 Toews]

Ive been having a great time trying to replicate this problem and thought
maybe if I posted some results someone else might have a brainwave !
First, and in the context of binding to a pass through query, the problem
seems to be related to the complexity of the query. The delay is still there
with a simple "select field from table" but is much less evident.
Secondly, the form itself is designed relatively quickly .. but does not
appear for a long time (presumably because it is trying to map the data)
Third, any attempt to make design changes to the form fail because of the
delays noted previously.
Fourth, this problem is not present in Access 2002 or with Access Project.
I have been able to replicate on 3 clean machines, each with a fresh build
of Access 2003.
I intend to try an earlier MDAC to see if the problem still persists
..unfortunately work keeps getting in the way and I havent yet had time.
Finally, I am using a complex pass through query against SqlServer 2000
which runs efficiently returning data over the network with impressive
results.
I have also used the same query but as a stored procedure, binding the form
to the stored procedure using a pass through query (i.e. exec sProcTest) this
results in the same problem.
Im having fun trying ..but maybe someone already has a fix for this problem
in Access 2003.

However I have very little experience with Access 2003, MDBs and SQL
Server.

I wonder though if you created a pass through query based on this
other much more complex query if that would simplify things so Access
wouldn't take so long. I rather doubt this will help but it's worth a
try.

I would suggest reposting with a subject something like "Access 2003
poor performance against SQL Server while in design view" to get other
folks to review your posting.

Once you start a new thread then I will also get MS involved in this
problem. I don't want to get them involved in a thread with two
sets of problems.

You sound like you've done some thorough trouble shooting on this
problem.

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

 

[R. Wilson]

Does anyone know if this issue has a fix. I am experiencing 10-30 second
delays on some forms. It is very difficult to get anything done.