[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 380
  • Last Modified:

microsoft access has encountered a problem and needs to close

Hi Gurus
Strange one!  I am getting this stupid dreaded message on one of the my databases on my machine.  If I open the database on another machine no problem.  I have uninstalled and re-installed MS 2003 and service packed it and am still getting the same error.  I can't get into the design view of the forms so can't error check on my code.   I have been through the solutions but find nothing that can help me - any ideas?
0
caandal
Asked:
caandal
  • 7
  • 4
  • 2
  • +2
1 Solution
 
darenceangCommented:
Is it possible to see the details where the error occured?

Click-ON Send it to Microsoft
and than you can Click on 'details' where you can see
what module name causes the error like (VB6.DLL, MSACCESS.EXE,Unknown module name, etc.)

Just a thought....
Hope it helps....
0
 
rockiroadsCommented:
When u say you opened the database on another PC, is it the same steps followed?
at what point exactly does this error occur?
Have u disabled something which prevents access to design view? if its just via shortcuts, you could try opening using SHIFT bypass.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Was this database previously working on the trouble machine? Or did you copy this from a working machine to the trouble machine?

You might try reregistering DAO and MSJET. To do that, click Start - Run and enter this:

regsvr32 "C:\Program Files\Common Files\Microsoft Shared\Dao\Dao36.dll"
regsvr32 "C:\Windows\System32\MSJET40.dll"

Of course, you'll have to change the paths to point correctly on your machine.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
caandalAuthor Commented:
Hi Rocki
The problem occurs from the main menu command buttons but it is caused by the underlying forms.   Same process is always followed.  I have also tried repairing, debugging and have not come right.  This is one of about 70 databases and is the only one that is giving problems.  I even went to backups as far back as July 2008 of the same database and same thing.
LSM  I think that your questions are answered above but the first regsvr32 falls over  - I think that you may be on to something - maybe that dll file is corrupt.  I am going to copy and re-register it
0
 
clarkscottCommented:
In design mode, click TOOLS and REFERENCES.
Look down the list and find what's "MISSING"

Scott C
0
 
caandalAuthor Commented:
Hi Clark
Been there done that.  If there were missing references it would be affecting other databases as well
tx
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
<f there were missing references it would be affecting other databases as well>

No, that's not true. While databases may share references, this specific database can have a reference that other databases do not. IOW, a bad/missing reference in DatabaseA has no bearing on the references in DatabaseB.

Can you post the references you have for the trouble database?

If this is the ONLY database causing trouble, and all of your 70 databases are running on the same machine, then you most certainly have troubles with that specific database, and not with other libraries. You might try build a new, blank database and importing all of your objects to that new database. If that doesn't work, you might try importing your objects one-by-one until you find the one (or ones) that cause the trouble, if that's what the trouble is. It's entirely possible that your backup from 08 is corrupt.

when you say you can't get into design view: I assume that, at some point, you were able to do so, and we're not dealing with a .mde format file? Can you open ANY object in design view? A module, or table, or report, perhaps?

RE: the RegSvr32 call for dao:

The file is actually name DAO360.dll ... although I don't think this is your issue, since you've now said that there are other Access dbs on the same machine running fine.

0
 
caandalAuthor Commented:
Hi LSM
Thanks - I have already completely rebuilt this database.  As I said previously it opensfineon other machines just not on mine.  I am aware that the dll file is the DAO360.dll.  As I said - this is a strange one.

I have to admit that right now I am inclined to reformat and reload my machine.
Cheers
Alan
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
< As I said previously it opensfineon other machines just not on mine.>

Do your other Access databases work on your machine?

Can you post your references from the trouble db?

Was this db developed on your machine? How is it deployed (i.e. copy/paste, or is there an actual installer that does this)?
0
 
caandalAuthor Commented:
Hi LSM

Copy and paste.  I am a database developer and often test stuff like this accross my network and on individual machines.  This db was developed on my machine. I am not quite sure by what you mkean about posting the references?
tx
Alan
0
 
clarkscottCommented:
Check the arrangement of the References on a 'good' pc and then compare to the 'bad' one.
The 'priority' (where on the list) reference files appear can have an impact.
Also, if you've upgraded Microsoft office (for instance) on your pc and not the others - this could have an affect.

Not all reference sources are reliant on renaming their version.  You may have installed software that overwrote an existing dependancy file and the 'new' one doesn't work.  Check the path of each reference on a 'good' machine and then check the 'bad' ones.  You may want to copy & paste the 'good' references to the same path on the 'bad' pc.

This is most likely what's wrong with the 'bad' pc.  

Scott C
0
 
caandalAuthor Commented:
Hi Scott C
That may well be the problem - I have installed bothe visual studio 2005 and 2008 for another project that I am working on.  I think that these issues only started after I installed that
Alan
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
To check your references:

Open your database, then go to the VBA Editor window (Ctrl + G will get you there). Click Tools - References for a listing of the references you're using in that database. If one is marked MISSING, you'll have to fix that before you can run your database successfully.

While you may be able to copy/paste SOME references to a different path, in most cases the items you'd reference themselves depend on other libraries/builds etc ... IOW, I'd be very leery of using copy/paste to fix references unless you're very confident that you require only that file to get the reference correct. In most cases you'd need to install that reference (in whatever capacity that entails) in order to properly re-register it. Access normally has no trouble working with references located at different locations. For example, my root drive is G, while most of my clients use C as a root drive. Many of my reference point to the G drive, some point to C and others point to my D drive ... when I deploy the app, however, my client's machines can successfully remake those references (this has to do with the way Windows handles references and the GUID associated with them).

0
 
caandalAuthor Commented:
Hi LSM
thanks for that - there are no missing references but as I said earlier I think that re-referencing my dll files may help
0
 
caandalAuthor Commented:
I re-applied Windows XP SP3 - problem went away
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 7
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now