Re: OO4O and locking records in multiple dynasets

Merci Michel,

The BeginTrans / Commit will indeed solve the situation in my posted example.

But I've decided to switch the locking strategy to an optimistic approach because (and this wasn't clear in my post now that I re-read it) the user can open different editing windows, all modeless, and the tables are accessed thru a single ODatabase object in memory. So as soon as one ODynaset::Update() is done, all other locks are released. This situation can't be tracked thru a transactions session.

Eric

Eric Lepage wrote:
> Hello,
>
> We're using OO4O 8.1.7.315
>
> Two ODynasets are connected to the same ODatabase. If both dynasets are
> issued a StartEdit() at some point, then performing an Update() in the
> second dynaset will release the lock in the first dynaset as well:
>
> ODynaset dyn1;
> ODynaset dyn2;
>
> ... connect, fetch records, etc.
>
> dyn2.Update(); // this release the lock in dyn1 as well
>
> Is there a global setting that can use to prevent this situation from
> happening? I know I can re-issue a StartEdit() on the first dynaset in a
> situation like the given example. But since the OO4O code is in a dll
> and this dll is accessed by multiple modeless windows, it is impossible
> to re-issue a StartEdit().
>
> Is it something that has been changed in later release of the OO4O library?
>
> Thanks,
>
> Eric Lepage
>
Received on Thu Dec 23 2004 - 08:00:14 CST