Todd Fisher wrote:

> If I recall the lock manager is a seperate process and must be
> started inorder for my application to access the database.

There is a separate process which is sometimes called gds_relay and
sometimes something like lock_manager. It exists to relay signals
between processes from different groups. If it's not running, processes
from different groups can't share a database - the second one hangs.
That's probably not far from what you want.

The danger you run is having some clever customer realize that the
database is firebird and decide to do some extra clean-up or reporting
or something using isql or some other tool. With lock management
enabled - without the lock manager / relay running - the other program
could only attach if the database were idle or the two apps were running
in the same process group. In the latter case, the lock management code
in Classic would keep them from overwriting each others changes and
corrupting the database.

Regards,


Ann