What are the Consequences of increasing MaxLocksPerFile setting? 1

[RippleJD]

I have a program that must process a large number of records in a transaction block. I was getting error 3052 "File Sharing Lock Count Exceeded." According to an article from Microsoft's Knowledge Base (and another in this forum), the recommendation is to increase the default setting of the MaxLocksPerFile setting. There is no mention anywhere of what impact increasing this setting will have. How much free disk space do I need if I increase the number to 15,000? 20,000? Are there any other pitfalls I should be aware of running under Windows environments (XP, 2000, NT, 98)?

Thanks!

JD

 

[ToeShot]

I may be wrong on this but if I understand what I have read correctly if you increase the MaxLockRecord size it should not have a negative impact. it will require more memory to store the records obviously. But a possible scenerio

Access stores files in 2K block sizez now all your info on a particular record may have a size 9K which resides on seven blocks
Block 1 2K
Block 2 2K
Block 3 500
Block 4 2K
Block 5 1.5K
Block 6 500
Block 7 500

so you have 7 blocks of memory being used on that record but four of the blocks are not using the full 2K of memory. Those blocks also contain information of other records but since those seven blocks are locked any information on the Four partially full blocks hince locking records that may not be open so other people may not be able to edit them. That's just the way Access works. So when you increase the recordlock size then you may indeed lock more records then what yop actually are seeing and/or editing.

HTH Dave
ToeShot@Hotmail.com
Today Is Tomorrows Yesterday. So Why Wait