Hi,

>> LockFile can be set in configuration and fb_lock_print use that one too.
>> Also the lock-filename can be passed with fb_lock_print, so i don't see problems here?
>
> A single fb_lock_print executable cannot handle different versions of
> the lock tables. Would you suggest to name it fb_lock_print10,
> fb_lock_print11 etc and deliver along with the appropriate engine providers?

Yes, For example fb_lock_print11 can handle engine11.
Or a general fb_lock_print could only look for version and redirect the arguments to the right
fb_lock_printXX?

Regards,
Arno Brinkman
ABVisie

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
General database development support:
http://www.databasedevelopmentforum.com

Firebird open source database (based on IB-OE) with many SQL-99 features :
http://www.firebirdsql.org
http://www.firebirdsql.info
http://www.fingerbird.de/
http://www.comunidade-firebird.org/

Support list for Firebird and Interbase users :
firebird-support@yahoogroups.com

Nederlandse firebird nieuwsgroep :
news://newsgroups.firebirdsql.info

--------------------------------------------------------------------------------
Mijn Postvak In wordt beschermd door SPAMfighter
1350 spam-mails zijn er tot op heden geblokkeerd.
Download de gratis SPAMfighter vandaag nog!