Hi.

We just experienced an odd phenomenon in Control Center.
One of my colleagues just performed a browse on a table and accidentally
changed a value in the resultset. He didn't press OK or anything, he
didn't even press enter to commit the change in the grid, he just
altered a value in a cell of the result grid.

But doing so, he made control center starting a transaction (but by not
pressing OK he did not end the transaction, so CC had an exclusive lock
on that record)

Why is this? Why doesn't control center just perform a transaction the
moment you press OK?

Or why doesn't CC present a warning light or something anywhere in the
screen indicating you're hogging the DB?

-R-

Jurgen Haan wrote:[color=blue]
> Hi.
>
> We just experienced an odd phenomenon in Control Center.
> One of my colleagues just performed a browse on a table and accidentally
> changed a value in the resultset. He didn't press OK or anything, he
> didn't even press enter to commit the change in the grid, he just
> altered a value in a cell of the result grid.
>
> But doing so, he made control center starting a transaction (but by not
> pressing OK he did not end the transaction, so CC had an exclusive lock
> on that record)
>
> Why is this? Why doesn't control center just perform a transaction the
> moment you press OK?[/color]

Wait wait wait...
I know this one myself..
Data could be altered and you could be working with phantom records.
[color=blue]
>
> Or why doesn't CC present a warning light or something anywhere in the
> screen indicating you're hogging the DB?
>
> -R-[/color]