I don't think it is a good idea to begin a transaction, display a page,
wait for a response that might never come, and then, if and when it does,
commit the transaction.
From what you are saying, it would sound better to carry the information
to the next page, and then, if the user clicks a button, begin the
transaction, execute the sql (via data objects in the context of the
transaction), and then, if all seems to be ok (each DO execute succeeded),
commit the transaction. Otherwise, roll it back.
-- Curt Springer, Team ND
At 12:05 PM 10/6/99 -0700, Neeraj Methi wrote:
>HI!
>1. I was wondering if I could do the commit of a transaction on the next
>page, that is the following page. So that the user can view the
>information before the user confirms its update or insert.
>
>2. I am getting transaction not active, when I try to execute my
>transaction. Is it
> compulsary to have begin() method in a transaction, because when
> I use begin(), passing
> the data source name, it hangs forever, displaying time out...
>
>I am working on ND 3.11
>
>Any advice will be helpful
>
>Thanks
>Neeraj
>
>_________________________________________________________________________
>
>For help in using, subscribing, and unsubscribing to the discussion
>forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
>For dire need help, email: [EMAIL PROTECTED]
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
