John F-
In general, if two users have a frontend open, but neither has a permanent
connection to the back end (like a recordset left open at startup), they
will fight each other to establish a new connection every time a new
object gets opened. The solution is to open a recordset on the backend on
startup and keep it open until exit. There will be some overhead in
opening the recordset if someone else already has the backend open, but
all other connections will share the already established one.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
-----Original Message-----
From: "jfakes.rm" <jfakes@rocketmail.com>
Reply-To: <MS_Access_Professionals@yahoogroups.com>
Date: Friday, November 23, 2012 8:32 PM
To: <MS_Access_Professionals@yahoogroups.com>
Subject: [MS_AccessPros] Slow performance in a split database
Ok here is another one of those weird ones.
I admin several split databases. In two of them, when I access the
database in a development frontend, I notice a huge slow down when another
user access the database using a different frontend. In one of the
databases, I only notice when one certain user logs in. When other users
log in (again different frontend) I don't notice any issues.
This only occurs in two databases and none of the other dbs. I connect
and have them are configured the same way (same versions, connection
method etc.).
Any idea why the slowdown on only two databases?
John F
------------------------------------
Yahoo! Groups Links
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar