kj01135 wrote:

>
> Thank you very much Raymond, that solve the problems.

You're welcome.

>
> However, if I want to do it the other way round and let the manager
> jobs to succeed by locking all the items being updated so that those
> items cannot be sold until the SP commits, what setting do I need?
>

It's not a single setting, unless you want to lock the entire table, which is not a good
idea in your application's environment.

I think IBObjects can allow you to do a dummy edit on all those records, and if so, you
could then try to create a dummy edit on each of the records in the single transaction.

If you do this, then you will most likely block the other users and slow down the whole
system with many retries from them rather than one manager re-trying.

Basically, you either update this kind of data when there's no-one on the system or in
one-by-one transactions. This is because the updates are completely independent of each
other.

Once you've updated the carrot-count, update the tomato-count, then update the
toothpaste-count, etc.
--
Raymond Kennington
Programming Solutions
W2W Team B