corrupt db??

H

Hafeez

My Access Database shows up as 92.8Mb in windows but when
I open it, I don't see the Database Window (pressing F11
does nothing).
I opened a different database and tried importing objects
from the 'bad' db, but had no luck (no pop-up box appeared
to help me select objects).

How can I recover info from my db? And is there anything
I can do to prevent this from happening in the future (the
db is sitting on the LAN)

Hafeez
 
J

John Vinson

My Access Database shows up as 92.8Mb in windows but when
I open it, I don't see the Database Window (pressing F11
does nothing).
I opened a different database and tried importing objects
from the 'bad' db, but had no luck (no pop-up box appeared
to help me select objects).

How can I recover info from my db? And is there anything
I can do to prevent this from happening in the future (the
db is sitting on the LAN)

Hafeez

Good luck... you may need it, especially if you don't have a backup.
Backups are ABSOLUTELY ESSENTIAL, for this very reason!

See Tony's excellent FAQ at

http://www.granite.ab.ca/access/corruptmdbs.html

for some suggestions about possible recovery and prevention. If this
is a single shared database, you should certainly consider splitting
it into a shared backend (containing only tables) and a distributed
frontend containing the forms, reports, and other user interface
features to prevent future corruption.
 
D

David Brown

This sounds very similar to what happened to us. One day
I tried to open our database and Access just sat there.
The bad news was it seemed that whatever corrupted it, had
happened a while ago, and all backups had been writen with
the error.

I went throught the recommendations. The one that worked
for us was importing each table one-by-one into Excel and
then back into a brand new database. Had to recreate all
the forms and reports, but at least the data was there.
 
T

Tony Toews

David Brown said:
This sounds very similar to what happened to us. One day
I tried to open our database and Access just sat there.
The bad news was it seemed that whatever corrupted it, had
happened a while ago, and all backups had been writen with
the error.

1) I personally have every CD backup I've ever made in my banks safety
deposit box. The largest they rent. Although in your case that's
user data so that's different.

2) You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Top