My database windows disapeared. It is open but I can not see it.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My database window disapeared before my eyes. It is open and by using the
arrow keys I can open my different tables but I can not see the database
window. I did not change the setting 'Display Database Window'; it is flagged.

How can I bring my database window back?
 
I have tried all that. It is not the problem. The database window is open and
by using the arrow keys I can open the tables, it would not be possible if
the database window was disabled. The problem is that I can't see the
database window. And I don't think I did anything to make it disapear. It
just disapeared before my eyes ...
 
Okay, try opening the Immediate Window (Ctrl G), and then issuing a command
similar to this:

DoCmd.SelectObject acForm, "Customers", True

where Customers is the name of an existing form. Substitute an appropriate
name. You can use different objects as well, such as table, query, report:

DoCmd.SelectObject acTable, "ValidTableName", True
DoCmd.SelectObject acQuery, "ValidQueryName", True
DoCmd.SelectObject acReport, "ValidReportName", True


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 
Okay, now I have done that. I must say that I don't know anything about
visual basic. When I write it and press enter a box shortly flash at the
screen and the disapears. What should happen?
 
Thanks to both of you, but it is not that either. The database window should
be in front and activated and it is not decentrilized to one of the sites.
When I press 'hide' followed by 'unhide' nothing apears.
 
Thanks to both of you, but it is not that either. The database window should
be in front and activated and it is not decentrilized to one of the sites.
When I press 'hide' followed by 'unhide' nothing apears.

Okay, it's time for the shotgun approach...

Create a brand new database and immediately disable the NameAutocorrupt
feature (see: http://allenbrowne.com/bug-03.html for reasons why you want to
do this). Then import all objects from the suspect database into the new
database, one group at a time. In other words, import all tables (but not
linked tables), then import all queries, then all forms, etc. While Access
will allow you to import all objects in one operation, the experts at FMS,
Inc. (a Microsoft Partner), have stated that it is best to import objects one
group at a time (Reference:
http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).

Recreate any linked tables from scratch. Access can cache a lot of
information about linked tables, which may no longer be valid, so it's always
best to recreate the linked tables from scratch. When importing local tables,
make sure to check the option to import relationships, menus and toolbars,
and import/export specs. If any of the local tables in the source DB are
hidden, you'll need to first unhide them. You will need to set the checked
references to match the source database, along with any startup options set
under Tools > Startup. Going through this process often times solves
corruption problems, because you get a new set of the hidden system tables
(the tables whose names start with "MSYS"). These system tables are updated
appropriately as you import objects.

This may sound like a lot of work, but it really isn't. Creating a new
container DB, disabling NameAutocorrect, importing all objects one group at a
time, re-establishing any linked tables, setting startup options, and setting
references to match the source DB is usually a fairly quick procedure. When
you are in the Visual Basic Editor, in order to check that the references
match the source DB, you should do a Debug > Compile ProjectName as well.



Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
 
Sounds good, I will try that.

Tom Wickerath said:
Okay, it's time for the shotgun approach...

Create a brand new database and immediately disable the NameAutocorrupt
feature (see: http://allenbrowne.com/bug-03.html for reasons why you want to
do this). Then import all objects from the suspect database into the new
database, one group at a time. In other words, import all tables (but not
linked tables), then import all queries, then all forms, etc. While Access
will allow you to import all objects in one operation, the experts at FMS,
Inc. (a Microsoft Partner), have stated that it is best to import objects one
group at a time (Reference:
http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).

Recreate any linked tables from scratch. Access can cache a lot of
information about linked tables, which may no longer be valid, so it's always
best to recreate the linked tables from scratch. When importing local tables,
make sure to check the option to import relationships, menus and toolbars,
and import/export specs. If any of the local tables in the source DB are
hidden, you'll need to first unhide them. You will need to set the checked
references to match the source database, along with any startup options set
under Tools > Startup. Going through this process often times solves
corruption problems, because you get a new set of the hidden system tables
(the tables whose names start with "MSYS"). These system tables are updated
appropriately as you import objects.

This may sound like a lot of work, but it really isn't. Creating a new
container DB, disabling NameAutocorrect, importing all objects one group at a
time, re-establishing any linked tables, setting startup options, and setting
references to match the source DB is usually a fairly quick procedure. When
you are in the Visual Basic Editor, in order to check that the references
match the source DB, you should do a Debug > Compile ProjectName as well.



Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
 
It worked; and as you said it wasn't much work. I had to import the tables
one by one. When I imported them all at once the database window disapeared
again!

Thank you VERY MUCH for your help :-)

Kristoffer
 
Bucker, now my forms are not working prabably. The buttons in the forms are
not working and I can not make new ones. Do you know how to fix that too?

Kristoffer
 
On Thu, 26 Oct 2006 23:50:01 -0700, Kristoffer Barfod <Kristoffer
My database window disapeared before my eyes. It is open and by using the
arrow keys I can open my different tables but I can not see the database
window. I did not change the setting 'Display Database Window'; it is flagged.

How can I bring my database window back?

Sometimes it can just go offscreen. Try Windows... Cascade to bring it
back into view.

John W. Vinson[MVP]
 
Hi

When you import all objects etc. from one mdb to another Access does not
recreate the references. You may have to manually add any missing
references.

Open the VBA editor and click Tools then References see if any are missing.
Also, try compiling the code, click Debug then Compile...

Mark
 
It looks like you have fixed the problem, based on this later posting:
http://www.microsoft.com/office/com...faa500-5947-41f6-8776-24b9578b88bb&sloc=en-us

It's always best to keep posting to the same thread, until you have either
come to a resolution, or fully exhausted the issue. How did you solve your
problem?


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top