>
> Did you know you can define a COMPUTED BY field
> on your master table using a correlated subquery
> on the related detail records? If you have to
> have this field at all, at least it will be
> consistent on the database side. (Firebird
> throws an exception if a request attempts to
> update a COMPUTED BY field.) It won't solve the
> consistency problems inherent on the client side
> where the application workflow is not responsive
> to its own changes....understand well that IBX
> does not provide any mechanism to refresh a
> master record in the buffer when your detail
> record's triggers modify the real record at the
> server. You have to take care of that yourself by
> refreshing, i.e., closing the master dataset and re-opening it.
>

i like the latter suggestion. can you pass me along a sample ALTER
TABLE with an ADD ... COMPUTED BY ... so that i can see the syntax. i
tried a few variations but no luck.

thanx in advance helen and have a great weekend.

lucas