[AccessD] The Dreaded "Error Message: Error Accessing File. NetworkConnection May Have Been Lost."

I forget who wrote it now, but I disagree with a recent statement to the
effect that "VSS is overkill for single developer projects." No it isn't,
and now you know why. The alternative (which I have used extensively as
well) is a new MDB|ADP every hour or so, named and dated as such (i.e.
My_App_20030801_A.ADP). Either way the most you lose is an hour's work.

Way back (and I mean way back) in the days of CP/M, I used WordStar. I was
writing a screenplay, doing an all-nighter, and my housemate awoke and
plugged the toaster in, blowing the fuse onto which my computer was wired
and costing me six hours of ostensibly brilliant writing (when you lose it,
it's always brilliant)! Learned then, haven't been prone to a loss bigger
than an hour since.

May you be able to say the same soon.

A.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert Gracie
Sent: August 3, 2003 12:59 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] The Dreaded "Error Message: Error Accessing File.
NetworkConnection May Have Been Lost."



 Well it just happened to me, and I have about 11 hours worth of work that
maybe lost (is lost from what I have been reading)

 The problem is that I did have the "Office 2000 Service Pack 3" installed.
So since MS says this will stop the problem from happening in the future,
and obviously it does not, how can I protect myself.. Such a pain....!!!!

 What cause the corruption.... "Save As" some reports.....

 Any pearls of wisdom??


Robert Gracie
www.servicexp.com