Robert,

<< In the meantime I have installed the latest DBISAM version 4.26b1.
Creating an index on a table when the lockfile is full still generates the
"database full" error. I can whip up a testapplication if you're interested.
>>

No, I see where the issue is - the IF EXISTS processing is screwing up the
exclusive opening logic.  The two concepts are at odds with each other in
terms of determining whether the table exists (and can be opened).

<< Another strange thing I've noticed is that when you use
TDBISAMTable.DeleteTable, it looks like the entry IS removed from the
lockfile (that shouldn't be happening, should it?). >>

I'd double-check that.  The only time a table is even added to the lock file
is during table open (not creation).  There isn't even a method in the
DBISAM engine to remove an entry from the lock file's table list.

--
Tim Young
Elevate Software
www.elevatesoft.com