Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / January 2006

Tip: Looking for answers? Try searching our database.

Slow Forms Over Network Until Compact/Repair

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Aaron J - 28 Oct 2005 15:35 GMT
We just recently upgraded from Windows NT client OS to XP (I have no idea
what the network server is) and from Access 2000 to 2003.  I have some
existing applications that run very very slowly when the mdb is run from a
network share, and then run fine when run from my local harddrive.

The weird thing is, when running on the network, if I perform a
Compact/Repair database by going through the Tools menu, then the application
runs fine (just like when run from the harddrive), but as soon as I exit the
application and re-open it, it again is running slow until I hit
compact/repair again.  I have tried turning off the "Name AutoCorrect" and
setting all the sub datasheet names to "[None]".  

Any ideas why it would work fine after the repair?
david@epsomdotcomdotau - 29 Oct 2005 23:55 GMT
compact/repair brings the entire database into
memory. In your case, it is probably bringing
the entire file into your local Network Client
File Cache.

(david)

> We just recently upgraded from Windows NT client OS to XP (I have no idea
> what the network server is) and from Access 2000 to 2003.  I have some
[quoted text clipped - 9 lines]
>
> Any ideas why it would work fine after the repair?
Albert D.Kallal - 30 Oct 2005 02:32 GMT
Compacting re-sets some of the track name auto correct stuff.

I would try turning off track-auto name correct.

I would also get your setup correct. I explain how to setup and run your
application here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

note the comments in the above about a persistent connection.

The "persistent connection trick" will restore your database performance.
Check out the following list that includes the "persistent" trick here:

http://www.granite.ab.ca/access/performancefaq.htm

Signature

Albert D. Kallal   (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.members.shaw.ca/AlbertKallal

King James - 16 Jan 2006 19:46 GMT
Given that network drives are usually mapped by a login script on the
server, and use a letter range that is unaffected by luggin in a
camera or use drive, I'm surprised at your shunning of them.

Are there any performance issues?

Thanks,
Bill

>Compacting re-sets some of the track name auto correct stuff.
>
[quoted text clipped - 11 lines]
>
>http://www.granite.ab.ca/access/performancefaq.htm
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.