Thank you Allen,
For suggestion 1. I this to be done on the server (NT4.0) that stores
the database or from one of the client machines that cannot access it?
Suggestion number 2. I can open the sample Northwind database (I tested
this out and uninstalled and reinstalled access on two of the problem
machines) I did not know how to open the code window and will try this.
Suggestion number three. I am not sure that the same Office 97 CD was
used for all of the installs even through it is shared on a virtual CD
drive. The Win 2000's are OK, it is some of the 98's that are not. I
can open access on all of the machines as long as I don't try to open
that database, so I will check version numbers and patch's om all.
Suggestion Four. I am not sure how to do this. Should I just do a Find
files using *.dll? If I find dupicates (this would not be a shock), how
do I know which one to delete/rename? Are there particular dll's to
look for? I would not be at all susprised to find multiples of any
files or dll's and this could easily be the source of the trouble. I
have even found two copies of NT4.0 on the server, one renamed to
WINNT2. But, why would anyone leave it there for over a year? It's
gone now. Thanks for your suggestions and I will post what I find out.
Linda
Quote:
> Some things to check:
> 1. Partial corruption.
> Try decompiling a *copy* of the mdb, by entering something like
> the following at the DOS/Command prompt without Access running
> (one line):
> "C:\Program Files\Microsoft Office\Office\msaccess.exe"
> /decompile "c:\MyPath\MyFile.mdb"
> 2. References problem.
> Open any database (e.g. northwind sample mdb).
> Open the code window (e.g. press Ctrl+G).
> Check under References on the Tools menu for anything marked
> Missing
> 3. Version differences.
> Compare the version and patch of Access on the machines where
> the problem occurs to those that don't have the problem. From
> the Help menu, About, you should see "Access 2000 SR-1" etc.
> 4. Conflicting DLLs.
> Look for any DLLs that are duplicated across different folders
> in the machines that have the problem. Particularly, check
> the Windows folder, the Windows\System folder, the folder
> containing msaccess.exe, the current directory, and any other
> folders in the PATH.
> > If this is the wrong place to post this, please let me know what group
> > would be better. I am not programing in access, but am a systems
> > administrator of a small LAN trying to figure out whaht happened two
> > weeks ago.
> > I was looking for the reason that some of our computers are receiving
> > the following error trying to open an access database.
> > MSACCESS caused an invalid page fault in
> > module VBA332.DLL at 0167:6519ae9d.
> > In this newsgroup I read the message about a convert database with the
> > following error message.
> > MSACCESS caused
> > an invalid page fault in
> > module VBA332.DLL at 016f:6517daaa.
> > I think they may be the same error and I think that the database may
> > have been converted by one of our 2 users of Win2000.
> > However, we are running a mixture of Win98 and Win2000 on the clients.
> > The 2000 machines can open the database, some of the Win 98 machines
> > can open the database and some cannot. They receive the error at the
> > top of this posting.
> > Does anyone know why some machines cannot access the data while others
> > can? I have checked the VBA dll mentioned, they are the same file, time
> > stamp and size.I copied it anyway and replaced the file on a computer
> > that cannot access the data. No difference, I still get the error.
> > I would think it is the conversion problem except there are several
> > machines that work.
> > Some of the 98 computers can access the database, others cannot and
> > receive the error.
> > Help please as this is a database that the boss had created and he has a
> > special fondness for it. I am lucky that it works on his Win 98 and Win
> > 2000 computers.
> > Thanks much,
> > Linda
> --
> Perth, Western Australia
> Tips for MS Access users at:
> http://odyssey.apana.org.au/~abrowne
converted database