Re: multiple transactions in table

the behavior you report is not unusual for a PowerBuilder app developed with the earlier 5.0 version. this behavior is caused by a DataWindow control obtaining exclusive locks on all of the rows, and not releasing the locks until the DataWindow was closed. I would have thought that this problem was fixed by now.

We had to code around the problem, avoiding the use of the "lock management" natively performed by the DataWindow. (it's been awhile since we abandoned PowerBuilder, but if i recall correctly, the developers had to make almost all of the DataWindows "read only", and for "updates", they had to fetch rows using custom SQL, into a non-displayable dw or dwc, and then build all of the code for obtaining locks and performing updates.) i do clearly remember, however, that developing a usable, multi-user application with PowerBuilder was a painful struggle.

The developers were clamoring to use Delphi, and referring to PowerBuilder as "PowerChucker", due to the frequency with which the IDE would cause windows exceptions and crash. among the mantras uttered by the frustrated developers were "save early, save often"...i know it doesn't help you any, but i do "feel your pain"...

"Chirag (Mark) Patel" <patelc_at_mcss.cas.mcmaster.ca> wrote in message news:Pine.LNX.4.10.10102231120480.11925-100000_at_mcss.cas.mcmaster.ca...
> I am using Oracle 8.0 and Powerbuilder 6.5 to develop the database
> application. It seems that when multiple users log in to the application,
> the transactions (add,delete, update) seem to be occuring only for one
> user and for the rest of them, the screen kind of freezes and the
> application no longer responds.
>
> I am not in charge of Oracle, but my belief is that the DBA needs to set
> some roles or provileges in order for multiple users to get access to
> tables at the same time. So far, we "granted" previleges to the necessary
> users and the DBA says he has given the previlges to users for certain
> roles like insert, update, modify, etc. I tested it out yesterday and
> it worked fine, but this morning, the freezing issue came up. Is there
> anything else the DBA should set? I am not sure why it's freezing,
> probably because more than 2 or more people are running the program. Any
> suggestions?
>
>
Received on Sat Feb 24 2001 - 18:25:02 CST