Here's an example of what a cloned folder for the QuitlinePhaseII.mde file might look like (ie. F:\Data\Databases\Quitline\DB)
The vb script is a button clicked on in the Main Menu (see above post or Main Menu below where they can click the Quitline (Phase II) button to open the app) or users can run the Quitline7MonthMadison.vbs script in F:\Data\Databases\Quitline folder.
Users are taught not to get into the F:\Data\Databases\Quitline\DB folder (where all the cloned files are - this could be buried even further in more folders if need be) and users are told not to open any of the files in that folder. (If possible and ideally, this folder would be hidden.)
You'll notice that I can easily tell which users are currently using the Quitline program by looking for an *.ldb file associated with their loginID in the name of the file. When the user closes the file, the *.ldb file will go away and a new one generated the next time they open the program via the script. Looking at this folder tells me exactly who's currently in the application and when they last got into it. I can also tell if they got into the latest version by looking at the source (called: QuitlinePhaseII.mde) and compare the date/size on that file with the date/size of the file with the user's loginID within it. It doesn't hurt to leave these files within the ...\DB folder. They will get overwritten whenever the user opens the vb script next. If a user's *.ldb file happens to get corrupted for any reason (which will not lock out or affect any other users), they simply re-open the application using the *.vbs script or button and it will self-fix the corrupted *.ldb file.
There are pro's and con's to leaving the cloned files in the folder. I personally like the pro's of leaving them in the folder so I can see when the user last opened the app. If need be though, a routine could be designed to run to delete all the cloned file (but leaving the source file.)
Also notice that there is never a need to make the users close out of the application to copy new source (mde) code (since this is never opened but instead, used as a source to clone off of). The mdb file can be worked on in the development folder while users are in the application. An mde file is then created and copied to the \DB folder (again, while users are still in the application). I will then send out an email to all users telling them that new source code has been copied and (at their convenience) to close out of the app and simply re-open it again to see the latest changes (using the button on the Databases Main Menu or running the *.vbs script.) There is also no limitation on the number of users who can open the application since every user is essentially in their own cloned copy of the source code.