DATABASE DESIGN
Eliminate Bloat by Using Temporary Databases in Microsoft Access
Using temporary tables in your Access database can lead to database bloat. This technique leverages built-in features of Microsoft Windows to eliminate the problem.
Subscribers: Sign-in to activate download link -- Get an example file you can use to follow along with this article.
About this Article:
You've probably had situations where you needed to get data from an external source into your application but, for a variety of reasons, it wasn't possible to link to the data: It had to be imported. At the same time, you might have needed to do something with that new data, such as run queries to take the data and write it to multiple existing tables in your application, or do validations on the values in the table. So, you didn't actually require the imported data to exist in its original form after you were done. Although you can import the data into a temporary table and work from there, if the import is something that needs to be done on a regular basis, adding the data to the temporary table and subsequently deleting it quickly leads to bloat in your database. What you might consider doing in such cases is putting your temporary table into a temporary database. That is, after you're done with the raw imported data, you simply delete the temporary database to minimize the impact on your production database. In this article, find out about the code you need to create such a temporary database by taking advantage of some Windows API calls.
Keyword Tags: Microsoft, Microsoft Access Development, Microsoft Office Access, Programming, Temporary databases