Access Front-End performance
I recently rolled out a new database with front-ends on everyone's desktop and the back-end up on the server. When the users click on the icon it takes about 5-8 seconds to load the database. I'm guessing it's because it has to connect up to the back-end up on the server. But when I copy a new version of the front-end to their computers with some tweaks it now takes like 15-20 seconds to load when they click the icon. But then after that it opens within 5-8 seconds going forward. Why would it take so long that first time when I loaded a new copy of the front-end on their desktops? What makes that any different than any other time they click on the icon?
ASKER
That's what I was kinda thinking too. But is there a way to speed that up? What I don't get is why only when I replace the front-end it does this. Nothing has changed between the tables in the back-end that would make it load slower.
For option number 1, the only way to speed up would be deliver to the client the local tables already filled.
For option 2, I dont think there is much to do.
For option 2, I dont think there is much to do.
ASKER
How do I do that for option 1?
Sorry, but if you are asking this question, this means that you did not understood what I had explained as for option 1.
ASKER
No I don't understand. You say to deliver to the client the local tables already filled. What local tables are you referring to? All the tables are in the back-end.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok so bottom line it's the network connection? There is no new code in the new copies of the front-end. It was purely query changes so that couldn't affect the performance for the first time it's opened. I'll check the network connections.
Check your anti-virus to ...make sure the DB's are not being virus scanned.
I'd also add a stop to the app right at the beginning so you can pin-point if it's Access starting up slow or your application.
As for your backend linking, are you using a mapped drive letter or UNC? Try switching that.
Jim.
I'd also add a stop to the app right at the beginning so you can pin-point if it's Access starting up slow or your application.
As for your backend linking, are you using a mapped drive letter or UNC? Try switching that.
Jim.
ASKER
Hi Jim,
I'm using UNC mapping since not everyone has mapped drives to the server location. I'm assuming UNC is better?
Can you explain the adding of a stop at the beginning of the app to tell whether it's access or the DB?
I'm using UNC mapping since not everyone has mapped drives to the server location. I'm assuming UNC is better?
Can you explain the adding of a stop at the beginning of the app to tell whether it's access or the DB?
<<I'm using UNC mapping since not everyone has mapped drives to the server location. I'm assuming UNC is better?>>
Sometimes yes, sometimes no. There are various things in the network which can cause issues. Whenever you have a problem, it's best to see how both work and if one works better than the other, it pin-points an issue.
<<Can you explain the adding of a stop at the beginning of the app to tell whether it's access or the DB? >>
in the applications code as soon as possible, put a STOP in the code, say in the onopen event of the startup form.
Execute the app and note the time it takes to get to the STOP. From there, you can hit F5 for it to continue and time how long the rest of the start-up takes.
This will give you an idea if start-up delays are related to Access and getting the application open, or to things your application is doing. You should also compare that to just Access itself opening (no DB) as well.
Between the three times, you can then figure out where your slowdown is and what might be the cause.
Jim.
Sometimes yes, sometimes no. There are various things in the network which can cause issues. Whenever you have a problem, it's best to see how both work and if one works better than the other, it pin-points an issue.
<<Can you explain the adding of a stop at the beginning of the app to tell whether it's access or the DB? >>
in the applications code as soon as possible, put a STOP in the code, say in the onopen event of the startup form.
Execute the app and note the time it takes to get to the STOP. From there, you can hit F5 for it to continue and time how long the rest of the start-up takes.
This will give you an idea if start-up delays are related to Access and getting the application open, or to things your application is doing. You should also compare that to just Access itself opening (no DB) as well.
Between the three times, you can then figure out where your slowdown is and what might be the cause.
Jim.
1) You load certain values locally to the database and because of that, it takes longer the first load;
2) The first connection takes more time than the subsequent ones because maybe of some registering process.