> I don't know whether I've categorized this question
> correctly. My users are required to use sombody else's web
> site to send data to their web site's database. We also
> need to track the same data locally in our database
> (MSAccess converting to SQL Server 2000). The data creates
> a new record in both databases. To eliminate redundant
> data entry, a button in my VB6 app currently "pushes" data
> from fields in the app to the other party's web form. The
> form's submit button sends the data to the other party's
> database. My app intercepts the click event of the submit
> button and stores the data in our database. The other
> party's database (or asp web app, not sure) then returns a
> message box if the data has been successfully entered into
> their database. This solution works most of the time.
> However, there are times when the data gets stored in our
> database, but never reaches the other party's database.
> Effectively, half of a transaction. A better solution
> would be to store the data in our database from the OK
> button of the message box that is returned after the data
> is entered into the other party's database. Is this
> possible, i.e., to trigger an event from a message box
> that is returned from the web app or its database? Is
> there another approach that would prevent data from
> ocassionally being entered into only one database?