more info:
my application use odbc-api library to connect to database. before I
run the application, the value for oldest active is 7 and next
transaction is 13250. After i run the application, the oldest active
is still 7 and the next transaction has increased to 19082.

does it means that my application did not commit the activities to
database ?

I believed odbc-api is automatically commit the transaction to
database. I even purposely add function, SQLEndTran to my applicaiton
after some operation. the value of oldest active is still 7.

what should I do then ?

rgds, chooi-ting

--- In firebird-support@yahoogroups.com, Phil Shrimpton <phil@s...>
wrote:

> On Thursday 12 June 2003 21:33, you wrote:
>
> Hi,
>
> > Roughly how far apart can the oldest transaction and the Next
> > transaction be before you know you have a problem.
>
> In theory, no bigger than the number of concurrent transactions you
> application can produce. For instance, if your app only uses a

single

> transaction at once, and you have 50 concurrent users, if should

never get

> bigger than 50.
>
> In practice, it never quite works like that <g> The two warning

signs I look

> out for are
>
> - The difference not returning to 1 when everyone 'logs out'
> - The difference going above 3x expected concurrent transaction

count

>
> Phil
>
> --
> 10:07pm up 57 days, 11:00, 1 user, load average: 0.38, 0.12,

0.04

> ICQ: 760757 AIM: pjshrimpton Y!: pjshrimpton