Thanks lester.
I am fairly new (only 3 years at it). Yes I use these tables just as 'Cache'
tables as you say you do.
I am concerned about the reliability of 'in memory tables' (We get fairly
frequent power - gltches and cuts).
And the structure of the cache table required varies according to which main
table it is getting its data from.
So I either have to have quite a number of 'Cache' tables ready and empty
them as you say, Or I drop them after use and re-create a new one every time
I need to use one.

This works...but does it cause the Interbase Datatbase to grow unreasonably
??

<lester@...> wrote in message
news:3B72C13C.C5EEF8D4@......

> > But 1. I thought a temporary table would be more reliable and
> > And 2. I have not seen anything about 'Memory Tables' in Interbase
> > orIBO.
>
> You are obviously new it Interbase?
>
> In normal operation, you can build queries that supply the information you
> need direct from the original tables, so you do not need to resort to the
> tricks other databases use to present reports. You just generate the

report.

>
> I use a couple of in memory tables for some information, using memTable

which

> is compatible with TDataset, but I have been loosing some of those now

that I

> am getting a grip on other ways of doing things.
>
> If you need extra data stored on the server for each client, then Helen's
> approach of a single table which is filtered on ClientID. This table can

then

> be used transparently to feed other queries without having to edit the SQL
> for temporary table names.
>
> I also use local copies of Firebird, to cache data, and fill it from the

main

> database as required. In this case I just 'DELETE FROM XXX' when I want to
> start again.
>
> After all that, what are you trying to achieve, then we can perhaps

suggest

> an alternative approach.
>
> --
> Lester Caine
> -----------------------------
> L.S.Caine Electronic Services
>
>
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>