Re: 2002 database corrupt and unuseable after upgrading to Access

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

  • Next message: Martin Rajotte: "Error 8152: String or binary data would be trucated when using upsizing wizard to SQL Server" 
    Date: Tue, 8 Mar 2005 05:21:01 -0800

    Allen, I will try this once I can get to 2002 again. It was removed when they
    upgraded Office. Your tips sound promising and I'll let you know how it goes.

    Thank you,
    James

    "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!
    >
    >
    >

  • Next message: Martin Rajotte: "Error 8152: String or binary data would be trucated when using upsizing wizard to SQL Server"

    Relevant Pages

    • Re: SQL commad each time I open MS Word
      ... Opening this document will run the following SQL command: ... information from a database -for example, if your document is a form letter ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: Prevent database open if already open by a user
      ... I added 1 field to the receiving table and called it "Lock". ... this lock during the close operation, when the user exits the database. ... developing because this particular database needs to be set up for one user ... it does not prevent the DB from opening or operating. ...
      (microsoft.public.access.modulesdaovba)
    • Re: GP
      ... Are you using a database (.MDB) backend on your application? ... It is possible that the msgbox proclaiming the error opening the file is the ... What opens the first form? ...
      (microsoft.public.vb.general.discussion)
    • Re: MS Hot Fix 04-028 is now causing problems with Mail Merge
      ... > the databases automaticly opens a mail merge Word document ... > that is linked back to the database. ... > record in the Word Doc to the corisponding record that is ... Opening this document will run the ...
      (microsoft.public.word.mailmerge.fields)
    • 2002 database corrupt and unuseable after upgrading to Access 2003
      ... I'm seeking advice on an Access 2002 database with VBA code which will not ... The database was operating successfully under Access ... The database has an autostart form which displays a few seconds, ... opens the debugger to a module that isn't running at this point. ...
      (microsoft.public.access.conversion)