TS experts - help me out here

[pj]

Previous question on record locking problems drew no response. Two users hit
the same area in an Access 2003 SP1 db running on Terminal Services.
Constant record locking messages appear although they are in different
records.

To test if Access was the problem, set-up a 5 user LAN, divorced from TS on
the server. The same database was hit by the users over a 4 hour period. No
file locking messages, it all ran smoothly.
Q. What setting in Windows 2003 Server or TS impacts on file locking?

Same problem years ago on Novell. By substantially increasing the locks
allowed property, all ran well.
Any help appreciated.

pj

[David W. Fenton]

"pj" <[e-mail]> wrote in
news:X-********************@is.co.za:

Previous question on record locking problems drew no response. Two
users hit the same area in an Access 2003 SP1 db running on
Terminal Services. Constant record locking messages appear
although they are in different records.

To test if Access was the problem, set-up a 5 user LAN, divorced
from TS on the server. The same database was hit by the users over
a 4 hour period. No file locking messages, it all ran smoothly.
Q. What setting in Windows 2003 Server or TS impacts on file
locking?

Same problem years ago on Novell. By substantially increasing the
locks allowed property, all ran well.
Any help appreciated.

Have you gone through all the issues listed here:

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

I don't know of much else that could be to blame.

I'm running the same configuration on client Terminal Servers and
don't see any record-locking issues.

Are you using optimistic or pessimistic locking in your forms? It
always seemed somewhat counterintuitive to me, but the fact is that
pessimistic locking vastly increases record lock collisions --
optimistic locking is almost always the better choice.

Also, I've never used record-level locking in Jet 4, and never found
any need for it -- I've not got a single A2K app in production use
where users complain about concurrency issues.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc