MS Access Multiuser - Slow Forms Over Network Until Compact/Repair

Author

Slow Forms Over Network Until Compact/Repair

Aaron J via AccessMonster.com

2005-10-28, 11:25 am

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?

--
Message posted via http://www.webservertalk.com

2005-10-29, 8:24 pm

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)

"Aaron J via webservertalk.com" <u4807@uwe> wrote in message
news:56847099c0ba9@u
we...
> 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?
>
>
> --
> Message posted via http://www.webservertalk.com

Albert D.Kallal

2005-10-30, 3:25 am

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/AlbertKa...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

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

King James

2006-01-16, 8:25 pm

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

On Sat, 29 Oct 2005 19:32:05 -0600, "Albert D.Kallal"
< PleaseNOOOsPAMmkalla
l@msn.com> wrote:

>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/AlbertKa...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

Sponsored Links