Application with Database back-end becomes very slow as more users connect.

[david epsom dot com dot au]

Application with Database back-end becomes very slow as more users connect.
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10094456.htm

Slow because of the network client timeout setting, but an interesting
discussion of what was going on.
Unfortunately, there is not a definitive statement that MS Access was
involved, or what version.

(david)

 

[Sylvain Lafontaine]

They are probably speaking of any databases using byte range locking:
Access, FileMaker, FoxPro, etc.

 

[david epsom dot com dot au]

I'm not an expert, so I don't know if FoxPro would use
byte range locking as described in the article. (Which
describes sequentially attempting byte range locking until
a free range is found).

In Access as I understand it, you lock byte ranges that
do not correspond to byte ranges in the data file, and
you check the lock file until you find a free range.

On the other hand, if you are just trying to lock physical
records in a FoxPro table, you just lock the range that
includes the physical records, so there would be no reason
to walk through sequential byte ranges.

????

(david)