Hi Amit,
First, it is never a good idea to include a real e-mail address in a
posting. Doing so will only invite the unwanted attention of spammers, who
harvest e-mail addresses from newsgroup posts. I have removed your e-mail
address from this reply.
I have updated microsoft office 2000 with the latest version
Service Pack 3, correct? You should see this indicated if you click on Help
About Microsoft Access. Have you also updated the JET database engine and
your operating system? See the following KB article:
How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528
If this is happening on more than one database, I would try a detect and
repair (Help > Detect and Repair).
I would decompile the code first. With Access closed, click on Start > Run
and enter:
msaccess /decompile
The next database you open will have it's compiled "P" code discarded. Then
I would do a compact and repair (Tools > Database Utilities > Compact and
Repair Database) without attempting to re-compile the code. Then create a
brand new database. Immediately disable the NameAutocorrupt feature (see:
http://allenbrowne.com/bug-03.html for reasons why you want to do this).
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
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
