[AccessD] Separate mdb for housing temp tables

Hi Borge,

I also use many temp tables, and I do keep them in the front end.  To keep
the database small, I set the FE to auto-compact on close.  So, there is no
separate code to make this happen.

A regular repair/compact of the FE is a good thing to do anyway.  The FE
does have system tables which also grow as the database is used, so they can
be kept to a minimum size.  And, although I don't actually know what the
repair functionality accomplishes, I like the concept of fixing things
quickly.

If you still need to keep a separate db to keep temp tables and you want to
compact it regularly, reply back and I'll post the code I use to
auto-compact the BE on the server.

HTH!

Dan 
 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd- Subject:
[AccessD] Separate mdb for housing temp tables

Dear List,

I have an application that make use of many temp tables.
In an effort to reduce FE bloat and not having to automate an FE compact
I've been thinking of placing all temp tables in a separate
mdb placed in same folder as the FE and link the tables to the FE.

This temp mdb will exist in two versions:

FE_tempORG, mdb in compacted state -
FE_temp , the one where the temp tables are linked to the FE

The startup procedure of the FE will first up shell out and copy the
FE_tempORG over the FE_temp and then continue with checking
linking to BE and FE_temp, supply the login routine, etc. ...

I admit I haven't searched the archives, the answer may already be there,
but...

Is this a way to go, or do you have other suggestions?

regards
Borge