Front End Takes About 5 Minutes To Initially Load

[Tsango]

Hi there

I have 3 PC's on my Network accessing a back end which is sitting on the main PC.

i.e.
Main PC has Front End and Back End
PC 2 has Front End and is linked to Main PC's Back End
PC 3 has Front End and is linked to Main PC's Back End

PC 2 and PC 3 take about 5 minutes to load the intial main form. Once it is loaded the performance is ok. I have a Gigabyte network so know it's not just a slow network.

I have had a look at many other threads and also read http://www.granite.ab.ca/access/performancefaq.htm but nothing has helped.

Any ideas about settings in say the options page that I may have set wrong.

FYI I have Default Open mode set to shared, Default record locking set to No Locks, and Open databases using record-level locking ticked. Not sure if these are correct or if there are other settings to consider here.

I have also found that once you open the initial form once, it then loads quickly if you close it and then open it again, but if you close the database front end and re-open it it then takes 5 minutes again.

The only answer I have at the moment is to never shut the darn thing...!

Thanks in advance for any suggestions.

Oliver

 

[boblarson]

I experienced this one before and it was due to my having a ton of combo boxes and list boxes, and subforms that needed to be populated. I would suggest looking at your design and figuring out if, one - some data could be accessed using local tables that get updated periodically (mostly for static data that isn't likely to change often) and then also if you have subforms, to not load them until the user needs them.

 

[Fifty2One]

try clicking on...
Tools
Database Utilities
Compact and Repair Database

...may sound silly but lots of people forget to do this once in a while when developing and their access app has grown to a kazillion point 6 kajillobytes

 

[KeithG]

I agree with Bob I try to keep all static data in local tables located in the Front End.

 

[RuralGuy]

You might look at these suggestions; in particular the persistant connection. http://www.granite.ab.ca/access/performancefaq.htm

 

[Wiz47]

I agree with Bob I try to keep all static data in local tables located in the Front End.

Same here. I keep all the static data in tables on the fe and try not to depend on the be to load combos and listboxes unless it is absolutely necessary. It saves a ton of time on the initial loadup from the server.

 

[GaryPanic]

I saw some where that it might speed up the loading if the BE was not lost in a folder
X\:sytem\data\soenwhere\lost\another\location
where it might be better
x\:datafile\.xxx

keeping the location closer to the drive\netweok letter

might be rubbish ,but kinda makes sense

 

[Dennisk]

You can improve performance by installing the FE on each users HD

 

[Wiz47]

You can improve performance by installing the FE on each users HD

That's true. We've tried it both ways at work, and having a copy of the fe on each computer is a far better solution.

 

[Tsango]

You can improve performance by installing the FE on each users HD

Thanks for all the suggestions.

The FE is on each individual PC

I do as much as possible use local tables

I always compact and repair the database after making modifications

I have read all the info and done the suggestions in the persistant connection article.

HOWEVER - I have now fixed the problem. It was due to a lock table that I have on the database. The lock table was full so each tiem I generated a session ID for a new lock it already exsisted and it was taking ages to find a free session ID!

Totally my fault sio sorry to have bothered you with this...

 

[boblarson]

Hey, not a problem. Thanks for posting back with the results as that may help someone else in the future.