Gregg
greggs at msn.com
Wed Feb 18 14:11:42 CST 2004
Jim, After reading the Tech Info on it I was convinced that would do it. When I saw no change I thought maybe I missed a step or something. It turned out to be door #3 (below). My main form is open for the life of the app so I just connected it to a BE table. I went back and tried it with a dummy form and it worked!!! Thanks very much for your help! -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Dettman Sent: Wednesday, February 18, 2004 1:16 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Stumped on A97 Speed Problem Gregg, Thought for sure that's what you were bumping into. Only other thing that comes to mind is to check for any virus scanning that may be going on. Outside of that, I'm out of ideas. What I posted usually takes care of things. Jim Dettman President, Online Computer Services of WNY, Inc. (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gregg Sent: Wednesday, February 18, 2004 1:44 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Stumped on A97 Speed Problem Jim I implemented the opportunistic locking registry change. Added these data types one by one testing in between. \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameter s Value Name: EnableOplocks Data Type: REG_DWORD Data: 0 Value Name: CachedOpenLimit Data Type: REG_DWORD Data: 0 Value Name: autodisconnect Data Type: REG_DWORD Data: ffffffff The key did not exist before the change. Rebooted the server but saw no improvement. The other 2 suggestions I had already implemented. Any other ideas? -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Dettman Sent: Wednesday, February 18, 2004 8:07 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Stumped on A97 Speed Problem Gregg, Couple of things: 1. Turn off opportunistic locking on the server (OPLOCKS). This is covered in the MSKB and is a registry change. Most likely, this is what your seeing. OPLOCKS allows client side caching of files. When a user grabs a file, their granted exclusive use of the file. This allows the client OS to cache the file on the client side. However when a second user comes along, the server goes back to the first client, tells it that it can no longer have exclusive access. It then waits for the client to flush it's cache and agree to multi-user access. Then the server allows user 2 to join. With Access, OPLOCKS is a waste because JET already does client side caching and handles that on it's own. 2. Make sure all the users have full create/delete privilege for the directory where the MDB resides - If not, the last user out cannot delete the .LDB file. This can cause delays when reopening the BE. 3. In your FE, hold a reference to the BE for the life of the app - This avoids repeated opening/closing of the BE by JET and thus avoids all the associated overhead. Jim Dettman President, Online Computer Services of WNY, Inc. (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gregg Sent: Wednesday, February 18, 2004 8:07 AM To: Access Developers discussion and problem solving Subject: [AccessD] Stumped on A97 Speed Problem I have an A97 BE with multiple A97 FE on a Win 2K server. The Workstations are on 2K as well. When I open the first user's FE, it takes 5 seconds. When I open the second user's FE it takes 20 seconds. It doesn't matter which workstation is second... its always 20 seconds. The time difference seems to lie in a section of code on my main form that does 7 lookups and makes tabs and other controls visible or invisible depending on that user's parameters the employee table. I can optimize the code and reduce the time considerably but I am wondering why this is so... and what performance is it costing me in other areas of the program? Also, I have used the same technique at another customer that I have not tested as thoroughly but uses Citrix. Their database takes about 80 seconds to over the network but only 12 second on Citrix. Is there some file locking going on that shouldn't be? What's the deal? Gregg _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com