IN THE SPOTLIGHT: MDE to MDB Conversion Service
(also supports: ACCDE to ACCDB, ADE to ADP, etc)
IN THE SPOTLIGHT: vbWatchdog
VBA error handling just got easier...
" vbWatchdog is off the chart. It solves a long standing problem of how to consolidate error handling into one global location and avoid repetitious code within applications. "
- Joe Anderson,
Microsoft Access MVP
Meet Shady, the vbWatchdog mascot watching over your VBA code →
(courtesy of Crystal Long, Microsoft Access MVP)
IN THE SPOTLIGHT: vbMAPI
An Outlook / MAPI code library for VBA, .NET and C# projects
Get emails out to your customers reliably, and without hassle, every single time.
Use vbMAPI alongside Microsoft Outlook to add professional emailing capabilities to your projects.
Provided by Allen Browne. Last updated: April 2010.
A superseded version of this page is available if you are using Access 97 or earlier on Windows 95, 98 or ME.
Since the Access database is a single mdb file, you can lose everything if it becomes corrupt. This is a rare occurrence if the database is running on reliable local area network (or single computer) and database objects are not being modified.
Corruption is much more likely during development when forms and reports are being created and modified, and code is being written and debugged.
For suggestions on recovering a corrupt database, see recovering from corruption.
The easiest way to corrupt an Access database is to interrupt a write operation. The inelegant disconnection accounts for almost all corruptions.
If you experience corruption on a database that is not being modified (i.e. only data is changing, not forms, reports, ...), check these areas:
|Area||Cause of Corruption||Preventative Action|
|User||Switching computer off without closing Access. (Users rarely own up to this.)||Train users. Log users in/out of the database to see which users/computers are crashing out.|
|Power||Supply issues: spikes, dips, brown outs, outages, or tripping over the power lead.||Consider a power conditioner or UPS for each workstation.|
|Hardware||Overheating, inadequate power supply, intermittent components, device conflicts.||Troubleshoot and replace bad component/computer.|
|Software||Any application crashing and bringing down others.||Ensure the latest service packs are installed. Remove unnecessary software.|
|Network||Intermittent cable connectors, hubs/switches, network cards, inherently unstable networks such as WiFi.||Troubleshoot and replace network hardware.|
|Configuration||Sharing a single mdb file amongst users.||Split the database into front end/back end, so each user has their own copy of the front end.|
|Full disk||Insufficient hard disk space for the temporary folder and/or virtual memory.||Check the temp environment variable is valid, and the hard disk has hundreds of megabytes free.|
|Service Packs||Workstations on different service packs (particularly JET) can cause inconsistent behavior.||Download the Office service pack and the JET 4 service pack from http://support.microsoft.com, and apply to all workstations.|
Some basic steps can lessen the chance of serious loss: adequate backup procedures, periodic compacting of the database, and simply closing the database when not in use.
Your database will corrupt during development when objects and code are constantly being designed and tested. These tips will reduce but not eliminate corruption:
Rebuilding your file by importing everything into a new database is quite quick. The most time consuming part is laying out your relationship diagram again after every import. To avoid that problem, Stephen Lebans has a free utility to save and restore relationship views.
|Home||Index of tips||Top|
This is a cached tutorial, reproduced with permission.
Have your say - comment on this article.
What did you think of 'Preventing corruption'?
No comments yet.
Why not be the first to comment on this article?!
Have your say...