Hi,

> > > After a quick test, I do not see any difference between IB5
> > > and FB1 regarding
> > > locking of external files.
> > > In both versions I have to disconnect all users to unlock the file.
> >
> > Did you DROP the external table in your test?
>
> It did not occur to me that it is necessary to change matadata to unlock

the external file.

> Pretty harsh method, but it works. Thanks.
> (I did not find it described in release notes)

Isn't is easier/more logical to release the lock as soon as the last
transaction that is using the file ends? I know external files are not
inside of transaction control, but probably any SQL statements
that use the table are - right?

Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."