Can't open database

[Ray]

I am using Access 97 and developed a database that can run on most of
computers except one notebook computer. When I open the database, an error
message as below displays.

Microsoft Access

Microsoft Access has encountered a problem and needs to close. We are sorry
for the inconvenience.

If you were ..........

I clicked the Debug button on above error message and it came up another
error message as below:-

MSACCESS.EXE - Application Error

The instruction at "0x651b66ff" referenced memory at "0x00000000". The
memory could not be "read".
Click on OK to terminate the program

Can someone advise possible causes and fixes.

Thanks,

Ray

 

[Wayne Morgan]

First, since it is just the one computer, it probably isn't Access. However,
there are some steps to check on.

1) Do other databases work on this computer?

2) Are the patch levels different between this computer and the ones that
work? For example, have all of the Windows Update Patches/Service Packs and
all of the Office Patches/Service Packs been installed?

3) Do you have the latest video and printer drivers installed on this
computer?

4) Is this computer running some software that the other computers aren't?

5) Have you done a full scan of the computer for viruses and spyware?

6) Have you done a full hard drive check, including a surface check, to
check for drive errors (especially for bad sectors)?

 

[Ray]

Wayne,

Thanks for your suggestion. Below are my answers

First, since it is just the one computer, it probably isn't Access.
However, there are some steps to check on.

1) Do other databases work on this computer?

Yes, other databases work correctly on this computer except this one.

2) Are the patch levels different between this computer and the ones that
work? For example, have all of the Windows Update Patches/Service Packs
and all of the Office Patches/Service Packs been installed?

Both patches are up-to-dated.

3) Do you have the latest video and printer drivers installed on this
computer?

Yes, I have.

4) Is this computer running some software that the other computers aren't?

Basically, the major application programs are the same except one or two
different.

5) Have you done a full scan of the computer for viruses and spyware?

Yes, both show no problem.

6) Have you done a full hard drive check, including a surface check, to
check for drive errors (especially for bad sectors)?

I am checking now. So far, I have not seem any error.

Ray

 

[Wayne Morgan]

Another thing I thought to try and helps sometimes. Try clearing the Temp
directory. Close all programs so that none are using files in the temp
directory then clear it. Depending on your OS, there may be more than one to
clear.

The main one is located at
%temp%
From the Start|Run type
explorer %temp% and click Ok.

the secondary one is located at
%windir%\Temp
from Start|Run type
explorer %windir%\Temp and click Ok.

On a Win9x machine, these are probably the same location. On Win2k and
WinXP, they will be different locations. You may not be able to delete all
files in these folders if a background process is using them, but there
shouldn't be more than 3 or 4 left once you're done.

 

[Ray]

Wayne,

Many thanks for your advice. However, they have no use to my problem.

Ray

 

[Wayne Morgan]

Ok, if the computer can open other mdb files, the current file can be opened
on other computers, and everything is clean and up to date on the problem
computer then that only leaves a few things.

1) The copy of the file on the troublesome computer is corrupted. Try
copying a fresh copy from a computer where the file works ok.

2) You have a bad memory module or memory cache. Most likely the former,
since other programs would probably have used the cache area also but may
not have forced the computer to use as much of its RAM as the database is.
Other hardware problems are also possible. If any of this is taking place
over a network, a bad network card is also a possible.

3) The computer has something corrupted in the registry that this mdb is
trying to access. It may not be a call that you've programmed, it could be a
call to a Reference that has been set.