But the database can't be to blame because...I'm not going to rule the database out or the network connectivity to it. I think that the 2.1 SQL*Dev is just less affected by whatever is happening. On the 3.1 system for example, if I leave it idle for about 15 minutes, issuing a command hangs SQL*Dev hard (no response -- must kill with Task Manager). However, the 2.1 SQL*Dev is unaffected. I think that the hosting center has a firewall that is killing the connection and 2.1 simply recovers better from that. I may be way off base. Somewhere (think this forum) I found someone had encountered similar 'idle' behavior and used the SQL*Net EXPIRE_TIME setting to keep a connection from being seen as inactive long enough to be killed by the firewall. However, that won't help most of my problems because they aren't inactivity-related.