My.ADVISOR.com Sign-In
ID
Password

Member Center / Sign-Up
   
SUBSCRIPTION STATUS
If you are a subscriber to this publication, sign-in to access locked articles. To subscribe or renew go to www.AdvisorStore.com.
Go to Article
Advanced Search 

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.
By Doug Steele

THIS ARTICLE IS SUBSCRIBER-ONLY
To read this article you must have a current Subscription or Passport for:
DataBased.Advisor.com
or
MSpro.Advisor.com

If you have a correct subscription, sign-in (pink box) to view the complete article and access any Download.

Purchase or renew your Subscription or Passport at www.AdvisorStore.com.

Click this link for help with subscriber online access.

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.

Doug Steele has worked for many years with databases on mainframes and PCs. He has been recognized as an Access MVP for his contributions to Microsoft-sponsored newsgroups. http://I.Am/DougSteele AccessHelp@rogers.com

Keyword Tags: Microsoft, Microsoft Access Development, Microsoft Office Access, Programming, Temporary databases

ADVISORAMA
All glory comes from daring to begin.
-- Eugene F. Ware

ARTICLE INFO

DataBased.Advisor.com

Web Edition: 2007 Week 15, Doc #18944

Print Edition: May 2007, Page 33

SUBSCRIBER ONLY ARTICLE LOCKED


File: Get an example file you can use to follow along with this article.
Subscribers, sign-in for Download link.

Use of this or any other site, content, product or service of Advisor Media constitutes acceptance of Terms of Use.
Portions copyright ©1983-2008 Advisor Media, Inc. All Rights Reserved.
Reuse or reproduction of any portion or quantity of Advisor Media's copyrighted content, in any form, for any purpose, requires written permission.
ADVISOR®, the ADVISOR logo, and other names and logos that incorporate ADVISOR are registered trademarks, trademarks or service marks of Advisor Media, Inc. in the United States and/or other countries.
Other trademarks are used for identification, editorial or descriptive purposes and are the property of their owners.
Hosted by Prominic.NET Website powered by
LOTUS SOFTWARE
STEED23 posted 04/09/2007 modified 06/29/2009 03:09:59 AM ztdbms/ztdbms
domino-144.advisor.com my.advisor.com 07/04/2009 08:23:53 AM