| James Carpenter 2005-04-06, 8:05 pm |
| 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\msacce
ss.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@discu
ssions.microsoft.com> wrote in
> message
> news:ECDCB8AD-25D6-4624-8FB2- 0E7812578600@microso
ft.com...
>
>
>
|