Aage,

> I wonder if 1518 is a max block size.

The question remains: why am I getting multiple blocks for so little real
information?

> (You aren't using TTables, are you?)

Who, me? Perish the thought. The guy who wrote the app orginally, now
that's a different story. Yes, the app is using TTables in some places. In
particular, the configuration data is located in a very wide, single-record
table, so using a TTable is not unreasonable.

> I've also noticed _a lot of activity_ when accessing
> a database over dialup

Thanks for the supporting evidence.

Art Metz
AMetz@...

> -----Original Message-----
> From: Aage Johansen [mailto:aagjohan@...]
> Sent: Thursday, January 25, 2001 12:34 PM
> To: ib-support@egroups.com
> Subject: [ib-support] Re: excessive network traffic [LONG]
>
>
> Art,
> needs to be
> split into manageable chunks.

and would be interested to know how to lessen the

> burden. I got
> some improvement by making certain that queries were prepared
> just once.
> (You aren't using TTables, are you?)
>
> Regards,
> Aage J.
>
>
> You wrote:
> ...
> 4. // Is this query generated by the BDE?
> select rdb$owner_name, rdb$relation_name, rdb$system_flag,
> rdb$view_blr, rdb$relation_id from rdb$relations
> where rdb$relation_name = 'alarminfo'
> returns 1518+1518+1518+1246+170+
> 1518+1518+1518+1246+
> 1518+1518+1518+1450
> (=17774) bytes
> The "stuttering" of the value 1518 makes me wonder if the BDE
> (or possibly
> gds32) is attempting a query; timing out; and then
> re-sending. OTOH, the
> client doesn't resend. Could the server be looking for an ACK and
> re-sending if one doesn't come through?
> ...
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>