[AccessD] Separate mdb for housing temp tables

We have an app where the BE is on a server.  To speed up some very data
intensive queries/reports, we import some data/tables to a local work DB.
This way, the queries/reports go off of the local (or mostly local) data
which can be much faster some times.

Bobby

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Borge Hansen
Sent: Thursday, August 24, 2006 1:02 AM
To: Access Developers discussion and problem solving
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