"Tom Wickerath" <AOS168b AT comcast DOT net> wrote in message
news:BA4EE1C2-9B85-41D3-AF97-05A9CCC1CE22@xxxxxx
Quote:
> I disagree. I have had to increase this value many times in the past, even
> for *single-user* Access applications. A long time ago, I bumped this
> value
> up to 200000 on my PC at work. This has been fine for most situations,
Hi Tom,
No worries, I'll happily defer to your wisdom in this matter! I'm not an
Access expert, by any stretch :-) If you say increase MaxLocksPerFile,
that's good enough for me.
I still think many users increment it for the *wrong* reasons. I have
certainly had people come to me in the past with performance problems, after
they tried bumping up this value and it had no effect on their performance.
But it seems like increasing MaxLocksPerFile doesn't absorb too many system
resources, so the trade-offs, whatever they are, are not severe.
I never look at microsoft.public.access ... as I say, I'm not an Access
expert :-) Although when pressed, I can speak SQL Server, DB2, and Oracle,
with the best of them :-))
Best regards,
--
Andrew McLaren
amclar (at) optusnet dot com dot au