Subject | Re: [ib-support] building a mini-IBReplicator |
---|---|
Author | Helen Borrie |
Post date | 2003-04-05T09:38:31Z |
At 09:26 AM 5/04/2003 +0000, you wrote:
transaction? Create an SP on the target database to receive parameters
which are passed to it, via a prepared executable statement in your
application, from a query on the source database.
You can also automate this in a variety of ways, using the replication
components in IBO...
heLen
>Application A uses database A.I know you are using IBO, so why not run a multi-database
>Application B uses database B.
>
>Currently some data - routinely entered into database A - is printed,
>then manually re-entered into database B.
>
>The task is to find a way to trasfer this data automatically from
>database A into database B (after some processing).
>
>Ideally the trasfer should be immediate, using the After Insert/After
>Update triggers in database A, but I doubt that this is possible.
>
>In practice, an acceptable solution would be to write all
>updated/inserted/deleted data into an external file.
>
>When the user of application B click a given button, data is read
>from the external data and written into database B.
>
>Before I dive into code, does somebody know a better solution ?
transaction? Create an SP on the target database to receive parameters
which are passed to it, via a prepared executable statement in your
application, from a query on the source database.
You can also automate this in a variety of ways, using the replication
components in IBO...
heLen