Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MS Access 2000 crashes

Status
Not open for further replies.

Freebee2

Technical User
Joined
Oct 3, 2003
Messages
1
Location
US
Hi,
I have been working on a DB (Access 2000) that I developed on a laptop running under Windows ME. When I created a copy and moved it over to my desktop (access 2000 & win 98se), I notice after a while that whenever I right click over any field (in design mode)for whatever reason, I would get a page fault error and crash. I am now also finding that if I try to select a toolbar from the View Menu it also crashes with a page fault error. I don't even have to click on this one to cause the crash, the mouse pointer just has to pass over "ToolBar" on the pulldown menu. I tried creating test db's to see if the problem was due to the different O.S.'s, but there was no difference. Anything I created did the same thing. So, I tried installing all the relevant MS Service Pacs (sp1 thru sp3). I tried removing and installing access many times, but to no avail. I can't seem to find an answer or info that might point me in the right direction.
Thanks
 
Free,

If you consistently bring a known "good" app to your
desktop machine and it crashes, then you can rule out
the possibility that the app is faulty.

If the problem was local to one database, I'd suggest
that you do a compact/repair or import everything into
a blank database. But you say that it happens with
other databases.

Given that, its either Access (or one of its components)
or a windows problem. Do your other Office products work?
If so, then the problem revolves around Access.

When you installed, did you REMOVE access first? This is
an option with the installation software and should be
tried.

Wayne
 
Make a note of the exact error message and search the Microsoft Knowledge base, it may be a known problem.



Neil Berryman
IT Trainer
neil_berryman@btopenworld.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top