Yeah, I know, I still have a legacy app using 3.26 CS mode.

If I create a memory table from within a tdbisamquery component that's using a remote session, then destroy the component without dropping the table, will the table get dropped automatically or do I explicitly need to drop the table?

TIA,  

John

John,

<< Yeah, I know, I still have a legacy app using 3.26 CS mode. >>

Hey, if it works...

<< If I create a memory table from within a tdbisamquery component that's
using a remote session, then destroy the component without dropping the
table, will the table get dropped automatically or do I explicitly need to
drop the table? >>

With 3.x, you'll need to explicitly drop the table.

Tim Young
Elevate Software
www.elevatesoft.com

What about local tables?  Will destroying the table free the memory table on the local machine, or do these need to be explicitly dropped as well?

John


>>With 3.x, you'll need to explicitly drop the table.

Tim Young
Elevate Software
www.elevatesoft.com

Never mind, I ran some tests, and yes, local memory tables should be freed.

John

On 2/1/2015 11:12 AM, John Easley wrote:
> Never mind, I ran some tests, and yes, local memory tables should be freed.

Not using v3 here but out of curiosity is the behavior same as in v4 -
they're freed when app exits (or if you manually drop them) ?

Anything else would prevent in-mem table sharing IMHO.

Raul

I believe the behavior is the same for 3.x and 4.x - if memory tables are not
freed during application execution, they are freed upon termination.

John