Lester,

> >>How many indexes are being filled, and what actual data is
> >>being pumped in? (Can't see original post <g>)
> >
> > One primary on each table, one secondary on the detail table.
> > Most data is VarChar (file pathes) in detail table, also one blob type

text

> > in master table.
> > Actually master gets 2 records, detail 42 records (it's not a joke).
>
> At that size there should not be a problem. Out of interest,
> what happens if you DONT delete. Is the growth the same?

Program logic requires records being deleted.

> In
> which case something is wanting to see the 'missing' records.

In absolutely no case, never.

> >>I get 4-5Mb database with a couple of hundred train records
> >>- it grows while I am building 'working' space and then
> >>settles after 24 hours as old records get deleted every hour
> >>and new ones added.
> >
> > Currently my changed app. is running for 2 hours, actual size is 1.3 MB.

I

> > cannot say how size increases on each loop because the Windows Explorer
> > seems to refresh file size incorrectly but it still grows.
>
> This may be suggesting something. Windows will only see the
> size change when the file is closed. If it is not seeing a
> change, then the database is not getting closed, and perhaps
> it should be.

May be a hint.

> I think that I would make the same suggestion I made to
> another problem - IBLogManager.
>
> http://www.iblogmanager.com
>
> It has shown me a few niggles caused by automatic bits
> happening in the background, resulting in extra activity
> which in my case gave updates that should not have happened.
> Not saying it will help, but it is an eye opener <g>

Possibly interesting, I will take a look at it tomorrow.

Thanks again
Arno Garrels