Re: 2002 database corrupt and unuseable after upgrading to Access

From: James Carpenter (JamesCarpenter_at_discussions.microsoft.com)
Date: 03/14/05 

Date: Mon, 14 Mar 2005 11:45:04 -0800

Allen, your advice worked. I decided to try the decompile on A2003 after
removing the module from the problem in question (opened the database with
the SHIFT key down, which delayed loading the module long enough to delete
it).

Many reports had empty modules, which I've now removed. Thank you for the
useful advice!

James Carpenter

"Allen Browne" wrote:

> James, it sounds like you have a partially corrupted A2002 database. When
> converted to A2003, the corruption shows up, but you can still open/use it
> in A2002?
>
> If so, a decompile might fix the problem. Access keeps 2 copies of the code:
> the text vesion that you view and edit, and the compiled version that
> actually runs. If these two get out of sync, the project is partially
> corrupt. This is fairly common when you are altering the objects, especially
> if you edit the code while it is running (i.e. in break mode.)
>
> To fix it, try this sequence:
> 1. Make a backup of the A2002 mdb file, while it is not in use, so you get
> multiple tries at this.
>
> 2. Opn A2002. Uncheck the Name AutoCorrect boxes under:
> Tools | Options | General
> Explanation of why:
> http://allenbrowne.com/bug-03.html
>
> 3. Open the report named R_Agg_S_I in design view, and set its Has Module
> property to No. (On the Other tab of the Properties box.)
>
> 4. Compact: Tools | Database Utilities | Compact. Close Access.
>
> 5. Decompile, 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"
>
> 6. Open A2002. Compact again. Close.
>
> 7. Try the conversion to A2003 again.
>
> --
> 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.
>
> "James Carpenter" <JamesCarpenter@discussions.microsoft.com> wrote in
> message
> news:ECDCB8AD-25D6-4624-8FB2-0E7812578600@microsoft.com...
> > I'm seeking advice on an Access 2002 database with VBA code which will not
> > open in Access 2003. The database was operating successfully under Access
> > 2002, and was compacted and repaired before the 2003 upgrade was
> > installed.
> > It is a single-user database still under development; there are several
> > backup copies, all displaying these symptoms.
> >
> > The database has an autostart form which displays a few seconds, then
> > closes
> > and launches the main switchboard. Launching in 2003 generates the
> > Microsoft
> > Visual Basic message while the form displays: "An error occurred while
> > loading 'Report_R_Agg_S_I'. Do you want to continue loading the project?"
> > This refers to an empty class module.
> >
> > Clicking "no" produces the message "The VBA project in the database is
> > corrupt."
> >
> > Clicking "yes" gives the message "Invalid procedure call or argument" and
> > opens the debugger to a module that isn't running at this point.
> >
> > Opening the database with the shift key down bypasses the autostart form,
> > but then opening the VBA code produces the same sequence of errors.
> >
> > Converting the database isn't possible because it is already in 2002-2003
> > format. Compact and repair under 2003 generates the same sequence of error
> > messages and fails.
> >
> > Has anyone experienced similar problems? If so, how were they resolved?
> > Sorry so wordy; just trying to describe the situation as completely as I
> > can.
> > Thanks to anyone who can offer help!
>
>
>

Relevant Pages

  • Re: Multi users - different versions, problem with reports
    ... solution is to decompile the database and compile it using the lowest ... To decompile, close Access, and at the command prompt enter the ... rather than allenbrowne at mvps dot org. ... > from 1 table but not linked table (Invoices and Company Details tables are ...
    (microsoft.public.access.reports)
  • Re: Unwanted break mode @ startup Access 2K
    ... > This can happen if the project is partially corrupt, and a Decompile ... Compact the database to get rid of this junk: ... rather than allenbrowne at mvps dot org. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Access 2003 Downwards Compatibility
    ... decompiled the database in Access ... 2000, checked at Access 2003 the references, but no ... To decompile, enter ... rather than allenbrowne at mvps dot org. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Need code to run on DB close
    ... Initially the Db has the Shift key disabled. ... When someone opens the Db, an AutoExec macro calls a code that validates the ... So the Shift key HAS to be disabled every time the database is closed. ... last form closed then a startup form is perfect for running code ...
    (microsoft.public.access.setupconfig)
  • Re: There isnt enough memory? -- cannot open form
    ... When you tried the SaveAsText where were you? ... Try this - close the database then reopen it and open the VB Editor. ... > I've now tried "decompile" with no success. ... >> and keep a backup of the corrupt database. ...
    (microsoft.public.access.forms)
Loading