By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,983 Members | 2,082 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,983 IT Pros & Developers. It's quick & easy.

Delay in opening local tables in one profile but not another

P: n/a
I've got a performance issue in Access 2000 running on Windows 2000.
Opening a table local to the MDB takes about 1-2 seconds normally. If
I log out of the windows profile that is normally used on the machine
and log into another windows profile, the same table in the same MDB
file takes 6 seconds to open. I have tried setting the subdatasheet
property to [None] and turning autocorrect off, neither one changes
anything. Doing a compact/repair also has no effect. I do have a few
hundred tables total, most of them linked to a backend ODBC DSN, but
the behavior is the same whether it is a linked table or a local
table.

Does anyone more familiar with access 2000 have any idea what could be
causing this that would be specific to the user's windows profile?

May 7 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
See if Tony has any ideas that help; especially the persistant connection.
http://www.granite.ab.ca/access/performancefaq.htm

lo*****@gmail.com wrote:
>I've got a performance issue in Access 2000 running on Windows 2000.
Opening a table local to the MDB takes about 1-2 seconds normally. If
I log out of the windows profile that is normally used on the machine
and log into another windows profile, the same table in the same MDB
file takes 6 seconds to open. I have tried setting the subdatasheet
property to [None] and turning autocorrect off, neither one changes
anything. Doing a compact/repair also has no effect. I do have a few
hundred tables total, most of them linked to a backend ODBC DSN, but
the behavior is the same whether it is a linked table or a local
table.

Does anyone more familiar with access 2000 have any idea what could be
causing this that would be specific to the user's windows profile?
--
HTH - RuralGuy (RG for short) acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via http://www.accessmonster.com

May 7 '07 #2

P: n/a
On May 7, 6:24 pm, "ruralguy via AccessMonster.com" <u12102@uwe>
wrote:
See if Tony has any ideas that help; especially the persistant connection.http://www.granite.ab.ca/access/performancefaq.htm

lope...@gmail.com wrote:
I've got a performance issue in Access 2000 running on Windows 2000.
Opening a table local to the MDB takes about 1-2 seconds normally. If
I log out of the windows profile that is normally used on the machine
and log into another windows profile, the same table in the same MDB
file takes 6 seconds to open. I have tried setting the subdatasheet
property to [None] and turning autocorrect off, neither one changes
anything. Doing a compact/repair also has no effect. I do have a few
hundred tables total, most of them linked to a backend ODBC DSN, but
the behavior is the same whether it is a linked table or a local
table.
Does anyone more familiar with access 2000 have any idea what could be
causing this that would be specific to the user's windows profile?

--
HTH - RuralGuy (RG for short) acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted viahttp://www.accessmonster.com

Ok, I still am not sure why the slowness was windows profile-dependent
but I was able to stop the delay in opening tables by eliminating the
use of a group security file. All of the security that matters is
handled by the back end RDBMS anyways.

May 9 '07 #3

P: n/a
Thanks for posting back with your solution.

lo*****@gmail.com wrote:
>On May 7, 6:24 pm, "ruralguy via AccessMonster.com" <u12102@uwe>
wrote:
>See if Tony has any ideas that help; especially the persistant connection.http://www.granite.ab.ca/access/performancefaq.htm
[quoted text clipped - 18 lines]
>>
Message posted viahttp://www.accessmonster.com

Ok, I still am not sure why the slowness was windows profile-dependent
but I was able to stop the delay in opening tables by eliminating the
use of a group security file. All of the security that matters is
handled by the back end RDBMS anyways.
--
HTH - RuralGuy (RG for short) acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via http://www.accessmonster.com

May 9 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.