lost in 07 crash?

N

NetworkTrade

Access07 was working on a new version of an existing Access application; had
given it a new name BlahBlah-v2

when I closed it - it flashed a "can not compress" and implied that it made
a back up...

but now when I look in the folder with both Access and MyComputer I don't
see the file at all....

did a search on the name and nothing is coming up...

is it totally gone?? help
 
J

Jerry Whittle

Look into the folder holding the original BlahBlah database. It might be
there; however, the name could be something like db1.mdb or db1.accdb.

Next turn of Compact on Close in Options. I bet you now know why!
 
N

NetworkTrade

well I never found it....in the traditional sense of looking for it with
browser, Access or a search function

this is a Vista machine and Vista has a pretty nice ability to go back and
get a shadow copy (once I learned about it...) just right click on the
folder and go to 'Restore'

it was restored this way....and frankly turned out to be pretty simple....


On the otherhand; I'm pretty good at checking out Allen Browne's tips to
avoid corruption and I don't remember being warned away from Compact on
close....in fact I thought that Compact was considered to be a good way to
keep the db clean...

Would be interested to learn more on this point.

As to the crash; I've never seen this type behavior before (where it
disappeared entirely); but then am new to working with both Access07 and
Vista so these environments may explain the new behavior - my hunch of the
cause is that I was in the middle of linking to an Excel Table - and upon
hindsight that file had been emailed to me unzipped; and I think possibly it
was an underlying security control function that caused the crash...but will
probably never know...

Had the excel file resent to me zipped - and linked it fine (after
unblocking & unzipping of course). But that maybe is just a coincidence.

thanks for input though....
 
J

Jerry Whittle

I've had issues with compact on close. For one thing, a database seldom needs
to be compacted or repaired. They usually grow to a size that can handle
internal processes such as sorting and grouping. If you compact a database
then run a query that sorts and groups, the database just goes back up in
size again. Therefore there's a "working" size for a database. I typically
compact and repair manually about once a month.

Then there is the problem if Access is shut down in the middle of a C&R. If
you have a rather large, complex database, someone might get impatient while
it's shutting down and just power down the computer. Or in your case possibly
the computer stopped working midway through.

C&R is suppose to work by first creating a backup copy of the database named
something like DB1.mdb or DB1.accdb; compact and repair that database; delete
the original database; then rename the DB1 database to the original name.
Seems aobut right; however, it can go wrong.
 
Top