> Creating temporary tables is rarely necessary with InterBase (unlike e.g. MSSQL, > which has no other means to generate a multi-row result set from a stored proc.) > It's also a bad idea in a transactional RDBMS to have users creating and > destroying objects.

I have to disagree slightly with Helen, since I use temporary tables to
reduce network traffic. But Helen's solution still works, since IB6 is
free, you just add a local copy to keep lookup tables. The time taken to
build a local view is far shorter than the time downloading over a slow
link.

It is not as flexible as a single database, but when network access is
via poor 64k links it produces a more usable system.

If this is the reason you want temporary tables, but you can't deploy
Interbase, then another option is memtable, which you will find at
www.groups.yahoo.com/group/memtable
It provides a simple in memory database that can be used with BDE tools.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services