To Marshall Barton

[Bill Stanton]

Marsh,

I belief that the "Disaster Strikes Report" thread is stone
-cold by now, but I wanted to close with you on that caper.
A few hours after my last post, my graphics card went into
the tank and I lost my monitor, so I've been in the process of
getting a major hardware upgrade and software re-loads to
stabilize for the last week.

Anyway, it turned out that the corrupted mdb front end
extended back into the last production release but only the
inaccessible report that we discussed extensively was lost.
So, I created a new mdb and imported tables (mostly links),
queries, forms, reports and modules into the new mdb and
re-created the report that flushed out the problem in the
first place.

Thanks for your suggestions and guidance on finding the
best solution.

Bill Stanton

 

[Marshall Barton]

Marsh,

I belief that the "Disaster Strikes Report" thread is stone
-cold by now, but I wanted to close with you on that caper.
A few hours after my last post, my graphics card went into
the tank and I lost my monitor, so I've been in the process of
getting a major hardware upgrade and software re-loads to
stabilize for the last week.

Anyway, it turned out that the corrupted mdb front end
extended back into the last production release but only the
inaccessible report that we discussed extensively was lost.
So, I created a new mdb and imported tables (mostly links),
queries, forms, reports and modules into the new mdb and
re-created the report that flushed out the problem in the
first place.

Thanks for your suggestions and guidance on finding the
best solution.

You're welcome. Corruption is bad enough, but to have your
system go out in the middle of everyting else is a serious
bummer. Anyway, I'm glad you finally got it straightened
out.