At 12:06 PM 08-08-01 +0100, you wrote:

>OK - I should have put more though into my last email, i will try to
>explain the situation.
>
>I have a problem, but because of a Nondisclosure Agreement i cannot discuss
>the design outside of the dev group, so i am going to try to explain the
>problem without explaining the design, here goes.
>
>We have Database A - changes to A will require that changes are made to
>Databases B, C, D, .......... etc. Our program will be used to make the
>changes to Database A, but there are 3rd party programs that can make
>changes to Database A.
>
>The problem is that Databases B, C, D, etc must be updated no matter the
>source of the changes to Database A. I had hoped that it could be done in
>Stored Procedures as it would make rollbacks easier.
>
>I think that the only solution is to use a UDF.

A-ha, have a look at the one-way Replication Module in the new version of IB Objects. With this you'll be able to make a neat little NT service module to take care of propagating these cross-database changes. It can make use of idle CPU cycles too.

Regards,
Helen

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________