Erwin Craps - IT Helps
Erwin.Craps at ithelps.be
Mon Nov 1 11:23:12 CST 2004
There is a well known issue what concerns re-linking slowness for tables in a BE on a network server. This can be easely solved by keeping a reference open to the backend. This will speed up you linking to the backend but also opening forms, tables etc. Just keep a reference to the backend as long as the application is open. Close it when closing Access. Erwin -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hale, Jim Sent: Monday, November 01, 2004 5:52 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Network issues PLEASE ADVISE <Make sure the files are not being virus scanned at startup.> This drives me nuts. I have Norton System works and it virus scans all office files. I have been totally unable to turn it off. Do you know the secret? Maybe an exorcist? Jim Hale -----Original Message----- From: Jim Dettman [mailto:jimdettman at earthlink.net] Sent: Monday, November 01, 2004 10:01 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Network issues PLEASE ADVISE Couple tips here: 1. Make sure all MDB/MDE's are in the same format (JET 3.x vs 4.0) 2. *Always* keep a connection to the BE database while the FE is open. I do this by opening a hidden form bound to a table in the BE right at startup and close it when the app exits. This is critical. 3. Make sure the files are not being virus scanned at startup. 4. Turn off OPLOCKS (Opportunistic Locking) on the server. 5. Turn off sub datasheets 6. Turn off name autocorrect 7. Make sure all users have full read/write/delete priv for the directory where the MDB resides. 8. Make sure your distributing a compiled FE to clients. 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 S D Sent: Monday, November 01, 2004 9:24 AM To: accessd at databaseadvisors.com Subject: [AccessD] Network issues PLEASE ADVISE Hi group, I've got a MAJOR problem. I've got an A2K application with a BE and a FE. FE is installed on the local machine and the BE is installed on the server. Using WinNT Performance has always been soso. Not fast but not very slow either. Now we've migrated everything to A2k2 with WinXP. Performance is terrible times 10!! Opening the FE takes about 20-25 minutes. Opening a linked table takes 9 minutes same goes for tables in the FE itself. However, when I open the FE and if I open a table that is stored in the FE it opens directly, no problem. When I then open a linked table => bang back to 9 minutes per table (linked or not) Is it possible that this somehow has to do with A2k2?? I know in Access 2 (that is two!!) you had to change OPENFILES parameter thingies somewhere. Does Access 2002 also have such a setting that must be tweaked?? TIA Sander --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. -- _______________________________________________ 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 *********************************************************************** The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. As a recipient of this email, you are responsible for screening its contents and the contents of any attachments for the presence of viruses. No liability is accepted for any damages caused by any virus transmitted by this email.