Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!
  1.   Become a Supporter    ::   Make a Contribution   
    Target (Recurring Monthly): $200 :: Achieved: $98

Re: Access XP CRASH!! on opening VBA Editor Or Modules

Discussion in 'Information Technology' started by Bob, Nov 18, 2005.

  1. Bob

    Expand Collapse

    When you refer to the command prompt do you mean the old dos command prompt
    or under run in Start? I did try both areas and was unsuccesful.

    "Allen Browne" wrote:

    > No promises, but if it is the binary that is bad, this might work:
    > 1. Decompile a copy of the database by entering something like this at the
    > command prompt while Access is not running. It is all one line, and include
    > the quotes:
    > "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
    > "c:\MyPath\MyDatabase.mdb"
    > 2. Make sure that the Name AutoCorrect boxes are unchecked under:
    > Tools | Options | General
    > 3. Compact the database.
    > Any luck?
    > --
    > Allen Browne - Microsoft MVP. Perth, Western Australia.
    > Tips for Access users - http://allenbrowne.com/tips.html
    > Reply to group, rather than allenbrowne at mvps dot org.
    > "Luke" <Luke@discussions.microsoft.com> wrote in message
    > news:182EEA35-2748-4F52-8349-2C44B1FCB81C@microsoft.com...
    > > Please Help!
    > >
    > >
    > > I have written a lot of code for a database Ive been working on in a fully
    > > up to date, legal version of Access XP. Unfortunately, Ive been stupid and
    > > havent been creating backups.
    > >
    > > THE PROBLEM;
    > > When I try to open the VBA editor, trigger any code or view any module
    > > within the project, access crashes with that terrible message...
    > >
    > > " Microsoft Access has encountered a problem and needs to close. We are
    > > sorry for the inconvenience."
    > >
    > > This only happens with the one .mdb file. Ive tried exporting my forms and
    > > modules to a new blank .mdb file. This just moved the problem to the new
    > > DB.
    > >
    > > Is it possible to recover my code? What do you think is causing the
    > > problem?
    > > How do I avoid the same problem in the future?
    > >
    > >
    > > PLEASE HELP!
    > >
    > > Luke

  2. Loading...

Since you're here... we have a small favor to ask...

More people are visiting & reading SPN than ever but far fewer are paying to sustain it. Advertising revenues across the online media have fallen fast. So you can see why we need to ask for your help. Donating to SPN's is vote for free speech, for diversity of opinions, for the right of the people to stand up to religious bigotry. Without any affiliation to any organization, this constant struggle takes a lot of hard work to sustain as we entirely depend on the contributions of our esteemed writers/readers. We do it because we believe our perspective matters – because it might well be your perspective, too... Fund our efforts and together we can keep the world informed about the real Sikh Sikhi Sikhism. If everyone who writes or reads our content, who likes it, helps us to pay for it, our future would be much more secure. Every Contribution Matters, Contribute Generously!

    Become a Supporter      ::     Make a Contribution     

Share This Page