Hi Imax,
First, can you open other .mdb files successfully on this PC? Assuming your
answer is yes, then I'm going to guess that your existing database has some
slight corruption. Before doing anything else, make a copy of the database on
your XP system for safe keeping, in the event that you need professional
recovery services. There are many possible causes of JET database corruption.
Here are links to two good sites:
Preventing Corruption (Allen Browne)
http://allenbrowne.com/ser-25.html
Corrupt Microsoft Access MDBs FAQ
http://www.granite.ab.ca/access/corruptmdbs.htm
On the XP system, where there is no apparent error, try the following
sequence of steps:
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, onegroup at a time, into your new database. 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. Recreate any linked tables from scratch.
When importing local tables, make sure to check the option to import
relationships, menus and toolsbars, 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, and setting startup options and 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.
You'll want to re-create any linked tables from scratch, because 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.
Good Luck,
Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
:
Hi,
My database file name.mdb is working fine on Office XP. But when I
installed new Office 2003, I could NOT run the database file name.mdb. I
opened it for about a few seconds then it poped up the screen "Microsoft
Office Access has encountered a problem and needs to close. We are sorry for
the inconvenience." Then they tell me to send the error report to Microsoft
or Don't Send. There was no explaination of what type of error. I looked up
the Error Signature and the Offset number is 000a3246. Does anyone got this
error before? I need your help!
Thank you,
imax
