472,145 Members | 1,499 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,145 software developers and data experts.

empty screen opening Access 2000 database

Dear people,
after many efforts I'm putting my hope on you.
Last week I changed a lot of forms and reports in an Access 2000 database.
It all worked fine and I closed the database without any problems. But now I
can't open it!
When I open the file Access starts and I get an empty Access screen instead
of the database window. The filename isn't shown in the title bar. I have
tried repairing, but Access is finished in 0.5 seconds (database is 8 MB)
and nothing has changed. When I try to open the database in Access XP I get
the message the database needs to be repaired.
I tried starting with the SHIFT key and also the F11 option.. Without
effect.
Openening other databases is no problem, so Access is working. I also tried
to open the database on another PC with the same results.

Any suggestions?
Ronald Balk
Nov 13 '05 #1
4 1717
Hey Ronald

What I would suggest (this has worked for me in the past) is to create a new
database and to import all the individual objects from your broken one.

This usually solves your type of problem. However, you may avoid trying to
import any objects that you think may be corrupted.

Do not despair, I am sure it can be fixed.

Any questions??? Ask

- Nicolaas
Nov 13 '05 #2
WindAndWaves wrote:
Hey Ronald

What I would suggest (this has worked for me in the past) is to
create a new database and to import all the individual objects from
your broken one.

This usually solves your type of problem. However, you may avoid
trying to import any objects that you think may be corrupted.

Do not despair, I am sure it can be fixed.

Any questions??? Ask

- Nicolaas


And in future backup on a regular basis. This may mean backing up a copy
every few hours or when a significant change occurs. I always backup at the
end of the day and then work on a fresh copy.
I keep track by documenting changes in a Word doc, while the code is
commented (of course!) along with dates that can be cross-referenced back to
the document.
Nov 13 '05 #3
Thanks for the suggestion. But I forgot to tell I've also tried this.
When selecting the database and clicking OK to choose the objects to Import
the Windows closes and the chance to select objects doesn't come. Also
without any error.

I've given up and consider this as a lesson to make even more backups.
Ronald

"WindAndWaves" <ac****@ngaru.com> schreef in bericht
news:1i******************@news.xtra.co.nz...
Hey Ronald

What I would suggest (this has worked for me in the past) is to create a new database and to import all the individual objects from your broken one.

This usually solves your type of problem. However, you may avoid trying to import any objects that you think may be corrupted.

Do not despair, I am sure it can be fixed.

Any questions??? Ask

- Nicolaas

Nov 13 '05 #4
das mooi jammer dan!
Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Wayno | last post: by
3 posts views Thread by tornado | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.