Gregg
greggs at msn.com
Wed Feb 18 14:54:25 CST 2004
Guess I missed that "How to split a database 101" course. How embarrassing. Thanks again! -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of DWUTKA at marlow.com Sent: Wednesday, February 18, 2004 2:24 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Stumped on A97 Speed Problem Just an FYI, this is a VERY good practice to get into. Using the 'hidden' frmLink method is very easy to setup, and relatively fool proof, since the form closes with the db, so there is no real 'handling' necessary once it's setup. With Aggregate functions, it is an absolute must, because they will constantly connect and disconnect from the backend, which will really bog things down. Access 97's help file had a description/recommendation for this process in the 'How to split a database' section. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gregg Sent: Wednesday, February 18, 2004 2:14 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Stumped on A97 Speed Problem Drew, I thought I was but when I tried it a second time using a dummy form instead of my main form it worked!!! Thanks a heap! I chased this one a couple of days. :-( -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of DWUTKA at marlow.com Sent: Wednesday, February 18, 2004 1:35 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Stumped on A97 Speed Problem Are you maintaining the link to the backend? It's very easy to do. Create a table (anything will work, but I commonly use tblLink), just one field, no data necessary. Then, in your FE, the VERY first thing you need to do (after you verify the links are good), open a form bound to that table, in hidden view. That will create and maintain a link to the backend, and should speed things up quite a bit. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gregg Sent: Wednesday, February 18, 2004 7: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