>> 2. Why do you use a file and not a memory space? IMHO, a lock table is
>> (relatively) small and updated quite often so it can be a performance
>> gain to store the things in the memory which (today) is cheap.
>>
>>
> Lock file is a misnomer. The actual table is in shared memory. The
> implementation is different on different operating systems, but it's
> never accessed as file.

Forgive my ignorance, but then what about is this entire thread talking
about? What is the SERVER-A.LCK file from our server and how/from where
fb_lock_print collects the data which throws in the screen? Of course
there are (more or less) support questions, so feel free to not
response, even if I'll be glad if you will enlighten me. ("you" = not
necessary Jim only)

tia,

m. th.