donjules2k wrote:

> In reply to my own question, i supose you could make a stored proc
> wich calls another stored proc. Hence the sub stored proc "acts" like
> a temp table. This might be use full for summing or grouping values
> but useless if you wanted the power of a true temp table, such as
> updating values.

IF you need a temporary table, then just done create it on
the fly! I have a silly little job that needs several layers
to calculate it, so I have a table into which I build the
results and then use that. Knowing how to do it properly
without the intermediate table I could now drop it, but it
is not an overhead.

The one rule I enforce is 'Do not change Metadata on site'
and anything that allows that to happen - such as adding
tables - is kept to the development machine. I may be over
cautious, but I've never had the sorts of problems some of
my competition have when updating. The time taken to copy
live data to a new database is saved ten fold if the update
does not work :)

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