Gustav Brock
Gustav at cactus.dk
Mon May 16 02:19:24 CDT 2011
Hi Stuart It's a bit more sporty to create a separate temp database and tables from scratch with DAO. It is faster than copying a file. Initially, of course, it requires a bit more code but for people like you that's more or less a copy-n-paste experience. That said, for a POS setup - where, as you know, "everything" can happen - we use a nearly locked down Windows which doesn't much more than booting, connecting the network and printers, downloading the FE and launching this. When/if "something" happens or "doesn't work", just ask the clerk to reboot. Simple but brings peace for years! /gustav >>> stuart at lexacorp.com.pg 16-05-2011 00:17 >>> Another solution to Bloat is to use a split FE/BE and open you app via a cmd/batch file which copies a clean FE from a central location and then runs it. Slightly slower to open the app, but you then have your temp tables in the FE which will make then faster to use. -- Stuart On 15 May 2011 at 14:24, Darrell Burns wrote: > Jim, > <<And in regards to your tables, I'd put them in a temp DB and access > them via links, then kill the DB when you exit the app. You can > create the temp DB easily enough by storing templates for the tables > in the current DB and using transferdatabase to create the tables in > the temp DB.>>