> > It could be that you don't even need sessionids - what are you
> doing
> > exactly?
> > Alan
>
> Mostly reports but other operations also. I'm rolling up data from
> several tables and performing calculations on it for reports or
> display. I was rolling it all up into DBISAM in memory tables but
> this was too slow. I'm now using a series of stored procedures to
> roll it all up into temp tables. This is blazing fast but now that
> the temp tables are part of the database (instead of part of the
> local user's stuff), I'm concerned about multiple users running the
> same operation. I think the session ID sounds very feasible and
> easy to implement. Is there a better way?
>
> Steve
>

It will remain blazing fast if you just use the stored procedures you have
and make them selectable. They will behave like normal selects - you can
even use WHERE clauses on them to further define runtime requirements.
No need to temp tables in this context. Believe me - they are fast this way
too.
Alan