Hi Marc!

How's tricks? Anyway -- on to the problem ---

>
>I wonder if there is such a thing that could store the station and the log in name, and since we are at it, the timestamp, of locked records.
>

>I'm thinking of a kind of a meta table that would contain the name of the table that receives the lock, the primary key and then the locking information. Locking would proceed through a generic tablebase.lock() method that would maintain the meta table and/or return the locking information.
>
>The only problem I see is the length of the key of metatable.
>
>Anybody done (seen) something like that or does not think it could work, or has a better idea, for clients who's computers are scattered over different rooms on different floors?
>


You could do this if you like. SBT (accounting software) did something like this (and may still do AFAIK). If you need that kinda tracking, maybe you are better off moving the base tables to SQL Server and letting the SQL Server native transaction log do it for you.