From: mcstock@enquery.com   
      
   you don't really have a production environment unless you have an   
   application interface other than an ad hoc SQL interface   
      
   you should at least use something like MS-Access via ODBC to give the users   
   a reasonable way to insert/update/delete and search data -- or have some   
   PL/SQL stored procedures to control the transactions (COMMITS can be coded   
   into the stored procedures) or at very least some script files   
      
   meanwhile, SQL*Plus (which is what SQL Worksheet runs behind its Java UI)   
   has an AUTOCOMMIT feature which can be set in the global login file --   
   however, this commits after EVERY individual DML statement -- so if you've   
   got users typing in stuff like   
      
       delete from sales where sales_period = 47;   
      
   and they accidentally type   
      
       delete from sales;   
      
   there is no way (as in no way) to recover the lost data without   
   point-in-time database recovery   
      
   what is your 'production' environment? intranet? client/server? character   
   terminals? if you could post or email some more specifics, i could provide   
   some recommendations   
   ----------------------------------------   
   Mark C. Stock   
   www.enquery.com   
   (888) 512-2048   
      
      
   "DBAGUY"  wrote in message   
   news:b62aa846.0310221357.2c2e141a@posting.google.com...   
   > Any tools out there someone would recommend for Oracle.  Currently   
   > users are utilizing SQL Worksheet in the production environment to   
   > help support the clients needs.  They have continuously forgotten to   
   > issue commits during monthly processing which affects their production   
   > cycle.   
   >   
   > Besides coding one myself. Is there a dumbed down version of an Oracle   
   > tool that will issue autocommits?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)