Auto backup mdb file

Since data changes over times the QPE query processing engine may have a different optimization plan doe ideal data retrieval but if you never make that recompile happen, you will never receive that benefit. Only a compact can shrink the size back down. Since there is no way other than by experimentation to determine when this is the case, it is often best to assume it may happen and prepare for it. Search for the keywords of "decompile" or "compact. The warnings are out there, so I won't take responsibility if Decompile or Compact breaks your MDB file but if it's something you already know about and like to implement regularly, then consider the following ways to make that process simpler.

Before I launch into my solutions, remember what I said earlier. What follows is not an exhaustive list of how the above tasks may be done but rather a summary of how it has been handled by some developers, myself included. My suggestions are not necessarily the "best" way to do these things but are good enough that they are the methods I choose to use in my daily development work. Since I'm focusing on what I actually use to maintain my Access files, I'll begin with a utility that one has to pay for.

It's a utility created by my friend and fellow author Garry Robinson from Australia. It's called The Workbench and you can read about it, download a demo and purchase it at his site. I like this tool for many reasons. More importantly, it comes with many other features that make it invaluable to me. More to the point and as you can see in the screen shot, The Workbench offers options to Backup, Compact, Compile and Decompile as well.

I use these features every day. What this tool doesn't do is automate maintenance. While I use some FMS tools on a regular basis, this is not one I'm familiar with in practical application.

You can read more about their wonderful tools for yourself at the FMS web site. This is not an option I've ever implemented but it could provide a simple solution. I worry about the overhead accompanied with the process when the user tries to close the application. I don't want phone calls telling my program closes slowly. One developer suggested using the following VBA code to toggle the option on and off every 10 closes of the database or so. That's a reasonable option, I guess.

After Access opens, navigate to the MDB file you wish to decompile and open it. Monday, February 19, PM. You mentioned three options for backing up the Access database. I will like to try the second or the third option but I am unable to do either.

Could you show me how to do it. Wednesday, February 21, PM. Also do I have to keep Task Scheduler open. Should the database remain open? I am not sure exactly how it should be set up. Saturday, February 24, AM. Remember, for a proper backup you always want your database to be closed, not in use.

All the data is stored in the backend database while the user interface is kept in the frontend database. Since the backend database contains all the data, it is important to schedule regular backups for it. On the other hand, you can perform a backup of the frontend database whenever there is a change in design or interface.

This way you can save yourself from the inconvenience of performing a lengthy split database. Before you start the backup process, notify the users to log out as they will not be able to access the database during the backup process. To back up the backend database, follow the instructions given below:. Backup for a Frontend database is performed when there is a change in design or user interface. Follow the instructions given below to perform backup for frontend database:.

Save the database with a default name, having date and filename, so that you can easily search it whenever there is any requirement for database restoration. If you need any help, there's plenty of posts on how to split the db, and to distribute the front end files.

Just let me know and I can provide a few links to topics I've posted on this. Megalog: If you could help me with this issue, providing the links you mention, it would be much appreciated!! Thank you very much in advance!! Best regards. First, here's the How-To for splitting the db. MDE Files Read both thoroughly, and give it a try.

Just make sure you back-up your database first before doing any of this. How must the sharing options be set then? Or only in one of them? Which one then? Best regards from Barcelona Once you split, I dont think it matters how any sharing settings are placed.

What you'll be doing is taking all your data and putting it in the BE all the tables. This is a read-only version of the FE, that you distribute copies of to all the users. They then use their own FE, to connect to the shared data that is in the BE. This ensures the lowest chance of corruption to the BE data. Now, if this FE is fully developed, you only need to distribute this once to each user. If it's updated periodically, then you'll want to update the master MDB copy, and then re-distribute newly-created MDE's each time.

This can be automated a bit in the 2nd post I linked earlier. I'm asking that because I've been having problems with the conversion.

The only module I have is the MouseHook from Lebans website I would like to keep that module, because it is very useful for all the users ; however, the first message "comp. What could be the problem here?

What about leaving the Front end as it is an MDB file? Does it have a significant change in overall performance? Thank you in advance! But you should really track down this problem you're getting during the conversion.