To add some to DL's advice, I would try to solve the existing problem in
Access 2000 before contemplating an upgrade. Have you:
1.) Compacted the database recently?
Use Tools > Database Utilities > Compact and repair database to do this.
2.) Installed the latest updates for
a) your operating system
b) Office 2000 [ie. SP-3) and
c) the JET database engine (SP-8)
See the following Microsoft Knowledge Base article as a guide to performing
these very important updates:
How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528
3.) Disabled Name Autocorrect?
4.) Cleared your temp. folder of all the excess files that can build up over
time? These are likely located in the following folders:
C:\Documents and Settings\YourUserName\Local Settings\Temp
and
C:\Documents and Settings\YourUserName\Local Settings\Temporary Internet Files
If you have done all of this, and you are still experiencing problems, then
it is time to create a new database "container", and import all objects
(tables, queries, forms, etc.) into it. Here is my standard set of
instructions for doing this:
Create a brand new database and immediately disable the NameAutocorrect
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.
Good Luck,
Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
:
The msg advising to upgrade is usually a default msg shown when you are
using an older app, no longer supported by MS. It doesnt neccessarily mean an
upgrade will cure the underlying problem. Are you saying Access,
freezes/closes? Are any Events logged in Event Viewer?
You can upgrade only the single component however it may not be cost
affective when compared to a full upgrade. There also may be other issues
with an upgrade
__________________________________________
Our service database was built in Office 2000, the Access program. I am
constantly having issues where the page I am on has to close and I am advised
to upgrade program. I am attempting to get management to upgrade. Would I
have to upgrade the complete Office program to Professional Office 2007 to
get Access 2007 or would Access 2007 upgrade be sufficient?
