startup form very slow over network

[Softdog]

Hi guys. I am stumped with a 45 second delay when I startup my application. I get the delay on networked workstations only when another workstation is up showing the Main "switchboard" form. Each workstation has their own copy of VBA (not compiled) with networked versions having linked tables to the server's .mdb

It seems like the workstations know that the main form is up somewhere else and need to negotiate with it. All have the (Access 2000) Default open mode to Shared, Default record locking to No Locks, and Open database using record-level locking On.

 

[The_Doc_Man]

Might not be Access locking. Might be file locking with respect to the LDB file or the MDB file - at the WINDOWS level.

You might need to ask your server's administrator to look at system performance for you in a contrived test of this situation so you can identify the bottleneck.

 

[Softdog]

Thanks for your suggestion Doc_Man. I've looked into the Windows file locking and I believe it to be OK. Besides I only get the problem when the machine on which the BE resides is showing the main form. If it's not, then the networked applications come up in ~5 seconds.

I've been running without any Access security (no .mdw file and everyone Admins), so suspecting security I delved into that whole world, giving networked users Open/Run/Read permissions only, but absolutely no joy. I've tried running Database Splitter again: no improvement. Removing 90% of the controls on the networked application startup form reduced the startup time from 45 seconds to 35 seconds. That's something, but that's not IT.

I am officially well and truly stumped.

 

[RuralGuy]

Look into Tony Toews suggestions. Microsoft Access Performance FAQ Especially the persistent connection.

 

[John.Woody]

It sounds like this is the problem you're having.
http://support.microsoft.com/kb/150384/

HTH
John

 

[Softdog]

Oh Yeah Baby That was IT!!!

The persistent connection works beautifully. This has been dogging (sic) me for months! RuralGuy, Tony Toews, I can't thank you enough.

Appreciate your input too, John.Woody. I don't need to fix the timeouts though since with Access no longer attempting to delete the .ldb it's not a problem.

 

[RuralGuy]

I'm glad Tony and I could help.