Mike Rudolph
asked on
MS Access file empty after disconnecting from network.
Was working on my access databse when I lost power on my laptop. The Database was sitting on a network server. Now when I try to open the database again after logging back into the network I get "Your network access was interrupted. To continue, close the database and continue". But when I look at the database size it says 'zero' now. OMG! See attachment. Does this mean it's GONE! I hope there is a way to retrieve it.
Looks gone to me. Hope you have a backup. Is this the FE or the BE that you've lost?
ASKER
That's what I thought. It was the BE. I didn't split it yet. Fortunately it's only a week's worth of work but lesson learned!
I've never seen this happen with a BE. Were you trying to compact it? (don't ever compact the BE across the network. Either do it by logging into the server using remote desktop or copy the BE to your PC, compact it, and put it back) Usually updates to the BE are small and fast. This looks like there was a huge pending write that got interrupted.
ASKER
Yeah...I think I had compact on close checked. Okay...good point. Thanks for noting.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Pat!
You're welcome.
Some Additional advice,
Replace access databse by a real database like MySQL, DB2,,,,
Replace access databse by a real database like MySQL, DB2,,,,
if you have versioning enabled on the server, right-click your file, select Properties, go to the Previous Versions tab and recover the last file.
Jet and ACE are very sensitive to network interruptions and hard reboots. This is one of the reasons that experts always insist that the FE and BE are split and that each user has a personal copy of the FE that runs from his own PC. Also important but not always included in the list is never compacting over the network.
If you have the ability to use SQL Server as the BE, you will find that it is more stable and less likely to loose data due to a blip. The Access FE is still sensitive to blips but you can recover by closing and reopening the FE. However, there will be a learning curve associated with learning how to make an efficient Access FE when the BE is ODBC.
If you have the ability to use SQL Server as the BE, you will find that it is more stable and less likely to loose data due to a blip. The Access FE is still sensitive to blips but you can recover by closing and reopening the FE. However, there will be a learning curve associated with learning how to make an efficient Access FE when the BE is ODBC.