> > >I
> > >need to write a series of stored procedures to work against
> > >temporary tables that are created and dropped on the fly so the
> > >table names won't be known until runtime.
> >
> > This is *not* a recommended technique. Create "permanent"
> temporary tables
> > and implement a session ID using a generator. You can housekeep
> these
> > tables at idle times...
> >
> > /heLen
>
> I'm all ears for a better way. I started out with permanent
> temporary tables but couldn't figure out the multi user issues.
> Apparently, a session ID would resolve this. Where can I learn more
> about this technique? What happens when more than one user needs to
> run the same operation?
>
> Steve

It could be that you don't even need sessionids - what are you doing
exactly?
Alan