Hi everybody,

I have an application called Appender. It opens table and appends records from another table.

wait window nowait "Appending from "+ m.tcSourceFile+". Wait, please..."
append from (m.tcSourceFile)	&& Add source records to target table.

The target table could be used in buffered mode (and participate in Transaction) in another application at the same time. We have Novell Network here and we're running our applications from NT server (tables and applications reside on Server). Sporadically I have a Messagebox saying, what record is locked with only 'Ok' button. Pressing Ok continues the work.

What can I do to prevent this error? It's not trappable by our Error Handler...

Thanks a lot in advance.


>Maybe a bit late (also referring to my earlier message on this topic) :
>
>By now we've found out that my so-called Novell-error is about something completely different i.e. we overhere just didn't know;
>A File Lock will be consumed by Novell for every open file; look at the according Set, it even says literally "including open files".
>Now where 250 for this (per connection) is the default, the client is able to go beyond that anyhow (allows for 255), thus, without even one file explicitly locked. Further, I'm fairly sure that Novell will have some files open for the client, while the client itself has not (formally or so, anyhow doesn't use a filehandle for it). Few weeks ago I had it myself, and analyzed all; I could count around 235 open handles at the (btw Y2K) client, and 249 open files at novell (including Qxxxx files for printing or whatever).
>Concluded, the "bug" is that Novell defaults to 250, which should be (well) over 255 anyway. Of course no bug, but stupid.
>
>Peter
>
>
>>YOu can change the settings in Novell:
>>
>>http://support.novell.com/cgi-bin/search/searchtid.cgi?/10025341.htm
>>
>>Supported values: 100 to 400000.
>>Default: 20000.
>>
>>Increase the value of this parameter if users have problems running applications and receive messages indicating that not enough record locks are available. Decrease the value of this parameter if client connections are using an excessive amount of server resources
>>
>>Here are the SET-parameters you need to modify:
>>
>>(the default values are for NW4.11)
>>Maximum Record Locks Per Connection (default: 500, range 10 - 100000)
>>Maximum File Locks Per Connection (default :250, range 10 - 1000)
>>Maximum Record Locks (default :20000, range 100 - 400000)
>>Maximum File Locks (default: 10000, range 100-100000)
>>
>>A rule of thumb is to double the parameters and monitor if the problem persists.
>>
>>This means when the parameters had been at default, the parameters should be set at the server console to e.g.:
>>SET Maximum Record Locks Per Connection=1000
>>SET Maximum File Locks Per Connection=500
>>SET Maximum Record Locks=40000
>>SET Maximum File Locks=20000