🚀 go-pugleaf

Quinn Wildman (CodeGear Developer Support) wrote:

> Capture it in your client, which then forms an insert statement.
> 

I've done that in other features but I don't like it. I'm trying to
keep most of the application in Interbase and not require the client to
know what to do.
So in this case I display a grid of records to the user, who selects to
process one. My client just tells IB to process that record - and
passes key identifiers only. IB Gets that record itself, then does the
processing - it does the updates and in the case of an error, should be
able to record that too - in a field on the original transaction record.

This solution requires IB to do all that processing, then send an
exception to the client to process, and presumably know what the
database wants it to do with it.
And, since my feature allows the user to request that all displayed
records be processed, it means that everything can happen in IB -
unless there is an error on a record - then IB needs to ask the client
to process the exception message, after which the database process can
continue with all the other records. If the database could process the
messages, then the entire batch could be processed at the DB where it
belongs.

Would it be possible to create a UDF to make that message available?
Maybe the isc_  call could be put into a UDF.  There are some
capabilities described in the Embedded manual, I'm not sure if this
could be done in a UDF. But that would be very interesting.

-- 
Patrick Moloney