Re: 2000/2003 Reference Problems

Tech-Archive recommends: Fix windows errors by optimizing your registry

Okay, it did work without blowing up completely. We had two issues. First,
I have a reference to the Office Object Library 11.0, where in 2000 it is
9.0. When we first opened the mdb on the 2000 machine, 9.0 is referenced,
but 11.0 shows as missing. No problem, we just delete the reference and go
on. The other problem is that in the modules I have added, I specify Option
Explicite and apparently there is some code in the mdb that uses undimed
variables, so now I will have to go through and clean that up.

Thanks for the pointers.

"Allen Browne" wrote:

> If you use only the essential libraries:
> VBA
> Access
> DAO
> then Access will take care of sorting out the changes as you switch
> libraries.
>
> If you add other libraries, such as the Calendar Control, MS Graph, Excel,
> you are likely to run into problems. You certainly want to use late binding
> for the other Office apps.
>
> Decompiling is a separate issue to references.
>
> --
> 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:2F38118A-0B63-4FD8-96EA-6A105F8D8665@xxxxxxxxxxxxxxxx
> > Thanks, Allen. I will do some testing. I had thought of that, in fact,
> > but
> > had not really tried it because there are significant differences between
> > the
> > reference library file locations and names between 2000 and 2003. If I
> > use
> > this approach, will the machine that is still on 2000 keep its references
> > or
> > will it try to find the 2003 references?
> > One other thing I had done to try to resovle this was changing all the
> > modules that are manipulating Excel from early to late binding, but that
> > did
> > not resolve the problems.
> >
> > "Allen Browne" wrote:
> >
> >> 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.
> >>
> >> "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.
>
>
>
.

Relevant Pages

  • RE: Built in function errors.
    ... I have yet to work with 2007 and certainly not in a mixed environment. ... I've replaced UCase intrinsic function located in the Control ... ways of trying to match all the libraries but so far nothing has worked 100%. ... It is probably that these issues are not related to references. ...
    (microsoft.public.access.modulesdaovba)
  • RE: Built in function errors.
    ... I've replaced UCase intrinsic function located in the Control ... ways of trying to match all the libraries but so far nothing has worked 100%. ... It is probably that these issues are not related to references. ... updating the software on the client computer and reselecting all ...
    (microsoft.public.access.modulesdaovba)
  • Re: YASID: Gargoyles, but no rats
    ... There were some references to, I think, gargoyles that had ... libraries in town. ... or in the agents of a God. ...
    (rec.arts.sf.written)
  • Re: cycle through a table
    ... Doug Steele, Microsoft Access MVP ... "Phil" wrote in message ... >> program and object libraries that provide functionality that may be ... References to the specific library files, ...
    (microsoft.public.access.modulesdaovba)
  • Re: cycle through a table
    ... module as is: you have to run the SQL code using something like: ... >>>> program and object libraries that provide functionality that may be ... References to the specific library files, ... then go back in and unselect the reference you just added. ...
    (microsoft.public.access.modulesdaovba)