Re: 2000/2003 Reference Problems

Try decompiling the mdb using 2003 before giving the copy to the keeper.

To decompile, enter 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"
Then compact the database:
Tools | Database Utilities | Compile.

Access actually keeps 2 copies of each module:
- the text version (what you read), and
- the compiled version (the code that runs.)
Each version of Access uses different binaries for the compiled version, and
it is *very* common for Access to corrupt the mdb when it is trying to
manage different versions.

By decompiling in A2003 before you convert back, and then compacting the
database, you are discarding the A2003 binary. A2000 will then create its
own binary, and so the problem is solved. We have found it essential to do
this every time a database has been opened in a later version, before trying
to run it in an older version 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.

"Klatuu" <Klatuu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7369B3EC-5D55-4AAF-A989-A2DCD0C4C865@xxxxxxxxxxxxxxxx
>I am in a mixed environment. Some users have 2000, others have 2003. I
>have
> 2003 and do all the VBA coding. The Keeper of the DB is on 2000.
> I am working with my mdb is 2000 format; however, my references are for
> Office 20003.
> I have tried exporting from my copy to the "Master" and I have tried the
> Keeper importing from my copy to the "Master". In both cases, when the
> Keeper opens the Master, it corrupts the database and we have to reload
> from
> backup.
> The work around I have come up with is tedious. I copy all code to a
> wordpad file and if it is from a form or report, I delete the code and set
> the Has Module property to false. The Keeper then imports the objects and
> pasts the code from the wordpad files into the appropriate objects and
> compiles the database.
> This avoids the corruption, but the must be a better way. Had I not
> already
> read all I can find on references and their problems, I would not be
> posting.
>
> Thanks for any suggestions.


.

Loading