Hi:


<If I'm not mistaken when you mention FR connections, you mean
<Frame-Relay connections, right! And, if they are frame-relays, are
<those connections staying alive for the duration of the connection.
<They might be dropping intermittently(and reconnecting by itself), and
<that the user doesn't notice this happening, but Firebird will notice
<it. It's just a guess at this point, since someone on this list had
<similar problems in the past with FR connections. So, if a connection
<is dropped, that could explain the difference between the OAT and the
<next transaction. But, this could also happen if a user shuts off(by
<pressing on the power button) their computer without properly closing
<the application and shutting down the computer. The same can be said
<if they disconnected from the remote connection before closing the
<application.



I am using Frame Relay for the last five years and i had not any
problems.


<Also, does your application uses BLOBs a lot? There has been some
<known memory problems with BLOBs, but I don't really know if they are
<fully fixed.



I not uses a lot BLOBS.



<But, in relations to your case, the high memory usage
<could also be related to query sorts(this usually happens when an
<index can't be used to order the result set), and FB will use as much
<memory as it can, before using temp files on the HD.



The application has a grid component that has a method for order the
query and this may be applied frecuently.

this component is used in many forms.


<Also, I just noticed that you didn't mention if you are using FB 1.5
<Superserver or Classic Server. Can you specify which one, just for add
<clarity? I suspect you are using Superserver, but I just want to be
<sure.



I use FB 1.5 Superserver



Regards,



Santiago



[Non-text portions of this message have been removed]