>-- snip ---
>
>But here's another thought.....and I'm wondering if anyone else has done this;
>This is for private datasessions and because the database needs a separate open instance for each one, you could simply put your functions in the database as stored procedures guaranteeing that they would be accessible in the proper datasession. Anyone ever put generic functions in as stored procedures?
>
>Steve

Steve:

Sure. All the time -- but only procedures that are needed for some functionality very specific to the database. Otherwise you load up on general procedures that could better be placed in a general procedure or function library.

I wonder if George would share with us more of his findings on the relative speed of procedures vs methods -- especially any speed difference among calls to methods at differenct levels in the class and container hierarchies.

George: I'd bet this is worth an article in FoxTalk.

Regards,

JME