At 01:47 PM 07-08-01 +0200, you wrote:

>Perhaps...
>But..., I have got sometimes these errors myself and IB server is running in
>the same computer as progam and I haven't received any errors.
>
>How should I check uncommited work? I thought that I should commit (or
>rollback) after the user has finished all entries into master and it's
>details.

Sure; but it's a fact of life that you can't update a row that doesn't exist. An insert is one statement, an update is another - separate statements. If you want to keep all mixed mode work on a particular master/detail group inside one transaction so that all will commit and be saved or all will roll back and be cancelled together, you might look at using a stored procedure call (same procedure) on the EditSQL and InsertSQL of the detail set to achieve it. Pass all the columns to the SP as parameters and have the SP check for the existence of the row before deciding whether to insert or update...

What mechanism are you using to form the master-detail relationship?

-- helen



-- helen




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