> Hello, a couple of days ago I asked if people have the need
> for a set of components in IBO that interface with IB/FB in
> the Services API functions. The result from this list was
> full apathy: only Helen replied.
> Warning: this is totally unofficial info. Now I have Jason
> facing some pressure to implement OO wrappers for the
> Services API. I'm not sure how the issue turned upside-down
> in a few days, but it happened!

I should probably tell you that I have already revealed the services
API in the IB_Header.pas (for release in IBOv4) - and fixed a problem
with the enumerations previously defined for the services API.

I asked Jason for permission to do this because I wanted to get to the
function that would let me retrieve the location of the ISC4 database.
I have a functioning implementation of this added to the IB_Session
unit (again for release in IBOv4). I intend to use this capability to
allow the setup of database file "registration" in the ISC4 database,
and so prevent the need to define the database locations to the
application.

So, whatever else happens the API will be visible for those that want
to play. Whether Jason takes up the challenge to write a full OO
wrapper or not, the API functions will be there and able to be used.

Geoff Worboys
Telesis Computing