TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Single Sourcing and Thinking Bigger From:Gwen Thomas <gthomas -at- PAYSYS -dot- COM> Date:Mon, 14 Jun 1999 09:58:34 -0500
<snip_from_Klopfenstein, Ed>
Gwen: How do you handle the data? I've always been a little skiddish about putting reams of text into Access for fear it may crash. Is that bad thinking, or is there another way to handle the data?
</snip_from_Klopfenstein, Ed>
Ed:
You bring up a REALLY good point. Single-sourcing means "putting all your eggs in one basket." And so, you have to look at disaster recovery from a new vantage point.
If you have ANY questions at all about data integrity, it's a good idea to back up databases several times during the day (not overwriting each other) and to save several days worth of backups. (Corruption in just one table might not be obvious immediately.) If you have a network that goes down often and you're working with the database over the network, this is especially important.
BTW, years ago, Access 2.0 was notorious for crashing and corrupting data. The next version, Access 7.0, didn't have a big problem, although corruption could happen. Can't speak to Access 2000. I think common thought now is that for databases of any size you might as well move up to the new SQL that is built for a client/server environment.
Gwen Thomas
Knowledge Management Consultant
CIBER Information Services
