Re: AW: [dbforms] Database refresh problem SOLVED

[Bill Tribley]

To my knowledge there is no way the database could have reported back.  
There is no syntax to instruct a select as to what to do about locks. In  
Oracle, the select would just read past the locked rows, giving you the  
value the row had at lock time. In your case, the select ground to a halt  
waiting for the lock. Which is better? Probably depends on what day you  
ask the question...

Permitting user access via general purpose tools often wreaks havoc with  
back end systems if the users are not careful about transactions. That is  
why many companies prevent such activity, or permit it only to select.

Bill
On Tue, 10 May 2005 01:07:28 -0500, <[EMAIL PROTECTED]> wrote:
SQL Navigator was holding a write lock on the specific table entries  
while his changes were not committed.
Unfortunalety, dbforms didn't generate an error message (not even a  
timeout), but only hanged when trying to access such a locked entry.
cheers,
Daniel
-----Ursprïïgliche Nachricht-----
Von: [EMAIL PROTECTED]  
[mailto:[EMAIL PROTECTED] Im Auftrag von  
[EMAIL PROTECTED]
Gesendet: Montag, 9. Mai 2005 14:34
An: jdbforms-interest@lists.sourceforge.net
Betreff: [dbforms] Database refresh problem


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms