Stan,

The purpose of the IBO$SCHEMA_CACHE table is to prevent you from having to
delete the schema files and re-create them. Instead, you just need to
increment the proper items in that table to note changes. IBO handles it
from there.

I am working on some code to automate updating this table. I will send it
to Jason for inclusion when I'm done. It is not a real high-priority for
me right now though, so it will likely be a bit.

--Rhett

> From: "stanw1950" <stanw@...>
>
> I don't know what the purpose of the IBO$SCHEMA_CACHE table that you are
> using.
>
> Here's the way I do it. In the DataModuleCreate procedure I set the
> SchemaCacheDir (for a TIBODatabase component) like this:
> MyDb.SchemaCacheDir := ExtractFilePath(Application.ExeName) + 'Schema'.
> Our large application (12meg)is on a shared network drive (Windows NT)
> over a 10/100 network, so one set of schema files are shared by all the
> users (up to 50 at one time). When I have made changes to the metadata I
> kick all the uses out of the app (programatically), delete all the schema
> files, and run the application again. This recreates all the schema
> files. The app takes about 8-10 seconds to recreate the schema files and
> come up to the main screen. After that it takes about 3 seconds to start
> (for me or any user).
>
> In the schema directory I see 8 tables (although some are empty) -
> ClientSchmaVer.IBO, Computed.IBO, Defaults.IBO, IndexDefs.IBO,
> ProcedureNames.IBO, TableFields.IBO, TableKeys.IBO, and TableNames.IBO.
> You don't seem to have all the same tables. Maybe that has something to
> do with your IBO$SCHEMA_CACHE table.
>
> Also (obviously), the IB_Connection of all my IBO table, query, dsql, and
> stored procedure components is the TIBODatabase component.
>
> That's about all the help I can give you. Maybe one of the gurus (I'm not
> one of them) can give you some more insight into your problem.
>
> Stan Walker
>

--