PS. I forgot to mention that if/when you create the new database container,
in order to help cure corruption issues, you will need to reset any startup
options and any required references that were checked in the source database.
These settings cannot be imported.
Also, when importing local tables, there is an option to import
relationships and import/export specifications. You should place a tick in
this dialog.
Tom
_______________________________
:
Hi Len,
Glad I could help. Since I have helped you solve this problem, how about
going back to my first reply and marking it as an answered question? I'd
appreciate it if you would do this.
On your follow-up question regarding guaranteed corruption with Access 2003,
I really cannot say. Sometimes Access can get cranky. Usually, the easiest
cure is to simply create a brand new database, and then import all objects
(tables, queries, forms, etc.) from the suspect database into the new
database. Two recommendations when doing this:
1.) Do not import linked tables. It is better to use File > Get External
Data to create new linked tables, instead of importing existing linked tables.
2.) Although Access allows one to import ALL objects in a single operation,
the experts at FMS have posted on their discussion boards that it is better
to import each object type, one group at a time. In other words, import all
local tables, then import all queries, then all forms, etc.
The reason that importing all objects into a new database can often help fix
problems is that you get a brand new set of system tables. These are the
normally hidden tables whose names begin with MSYS. These tables are updated
appropriately, as you import each object.
Don't forget to disable Name Autocorrect (aka Name Autocorrupt) in all of
your databases. Sadly, this option is enabled by default in all new
databases. Here is a list of reasons why you should not rely on this
"feature":
Failures caused by Name Auto-Correct
http://www.allenbrowne.com/bug-03.html
Tom
_______________________________
:
Hi Tom,
Thanks so much for your help. I did what you suggested and all seems to work
fine without the reference. There is one other question. Before removing the
reference I could almost guarantee a corrupted (not repairable) database when
using Access 2003. Any thoughts on why this would happen. Thanks again. - Len
_______________________________
:
Hi Len,
MSOWCF.DLL sounds like the Microsoft Office Web Components functionality. I
think this is used with Data Access Pages.
The first thing I would do is to make sure that you even need this .DLL file
selected as a reference. It might simply be left over, as a checked
reference, after someone was experimenting with this file. Find a machine
that is currently giving the error message (ie. one where you have not copied
the DLL file to it). Open the database on this PC. Press Alt F11 to open the
Visual Basic Editor. Click on Tools > References. Are any references marked
as "MISSING"? If so, try unchecking the affected reference(s), after first
jotting down the names. Then click on the OK button to dismiss the references
dialog. Click on Debug > Compile DatabaseName. Does the code compile
successfully? If it compiles okay after removing a checked reference, then
you didn't need that reference in the first place.
For more information on missing references, see the following two articles:
Solving Problems with Library References (Allen Browne)
http://allenbrowne.com/ser-38.html
Access Reference Problems (Doug Steele)
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html
If my answer has helped you, please answer yes to the question that reads
"Did this post answer the question?" at the bottom of the message thread.
Tom
http://www.access.qbuilt.com/html/expert_contributors.html
_______________________________
:
We are switching to Access 2003 to our Students database and are getting the
error message "MSOWCF.DLL" file not found. When I take this DLL from machines
that are running Office 10 and copy it to Office 11 the application works
fine. What is this DLL used for and why do I have to manually copy it from
Office 10 to Office 11. - Thanks - Len
