How can I bring my database window back?
Try pressing the F11 key.
Tom Wickerath
Microsoft Access MVP
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
Access 2007 Info: http://www.AccessJunkie.com
"Kristoffer Barfod" wrote in message:
news:75DCEDA8-7555-4AEE...@microsoft.com...
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
http://support.microsoft.com/kb/314598
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.
Thank you VERY MUCH for your help :-)
Kristoffer
Kristoffer
If you are willing to send me a compacted and zipped copy of your database,
I will take a look at it for you.
Tom Wickerath
Microsoft Access MVP
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
Sometimes it can just go offscreen. Try Windows... Cascade to bring it
back into view.
John W. Vinson[MVP]
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
"Kristoffer Barfod" <Kristoff...@discussions.microsoft.com> wrote in
message news:053DFEF6-2362-4F3B...@microsoft.com...
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
__________________________________________