This sounds like the server is disconnecting from the Paradox session.   
   Have you updated your Firebird software?   
      
   Now, I trust you're not going to say that you're using the native BDE   
   Interbase SQL Link to access a Firebird database using a TCursor.   
   Because if you are then you are boldly walking into the cavern of a   
   vicious, fiery dragon without armour or a sword and not even your faith   
   in all things good will save you.   
      
   I can't stress enough that direct access to SQL server tables in Paradox   
   will cause grief. Tcursors are particularly prone to causing problems.   
   If you access a Firebird database using the native Interbase link well,   
   Firebird's had numerous releases and updates since the Interbase 6   
   code-base turned into Firebird 0.0.1 so something MUST have changed.   
      
   You will eventually confront the reasons why everyone says not to do it.   
      
   Gene De Guzman wrote:   
   > Hi All,   
   >   
   > I have a timekeeping system that is connected thru a mapped drive to a   
   > firebird DB.   
   > Everything works fine when a lot of people are coming IN & OUT.   
   > When the workstation is idle IDLE for about 1 hour, my IF NOT   
   > tc.qlocate(empID) would fail for all subsequent users and the user would   
   > need to exit my application and go back in (not logoff the PC but only exit   
   > pdox) and everything works fine again.   
   >   
   --   
   Tom Krieg   
      
   ---------------   
   http://www.krieg.com.au   
   Please use the contact page to contact me via email   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)