You could probably design a script which runs to delete the accdb when the user exits but I wouldn't advise it. I have it so the script clones the FE to a separate folder (which the user's don't normally access). I then look at the cloned db's to tell me when the user last opened the FE (which is always a plus for me.)
Note though: the user must still have read/write permissions to whatever folder you have it cloned to.
If the user exits the FE by non-normal methods, the "delete FE" script wouldn't run anyway and you'd still see the cloned FE.
I found it doesn't pay to try and run a script when exiting the FE since if the FE locks up on the user, the script again, wouldn't run. But putting your source FE in a separate folder and having it so the script clones the FE in that folder works very nicely (ie. LUName = "T:\58TH\MTOC\Database\WorkingFEs\MSIS.accdb")
Note also that you can put the vb script to clone/open the FE anywhere. The vb script doesn't necessarily have to be in the same folder as the FE. I put all my vb scripts in 1 folder (called DatabaseScripts) so users can easily open any FE without having to dig through the folders. You can even get fancy and design a menu type system (which can also be an accdb) to launch any vb script. I created a menu type system (but in VB).
Last edited by pkstormy; 02-13-10 at 20:39.
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)