Re: 2000/2003 Reference Problems

I'm in a similar situation with a 2000/2002 mixed environment and ran into
the References issue. I'm using the 2000 and have some users with 2002. My
workaround was to open a new database on a 2002 PC, set my references, save a
copy to my PC and then export everything into 2002 creating a 2002 "master"
using the 2000 format. I code in 2000, and export updates to the 2002
master. The 2002 master can be opened on my PC so I can test it.

I'm able to require all the users (small environment) to have the reference
file locations standardized. That is a bigger issue in your environment.
Without knowing the number of users have two potentially painful suggestions -
1) have the reference file locations copied/moved to the same path on the
pertinent users PCs
2) identify the various paths of the files, copy the reference files on your
PC to those folders and setup duplicate links

Without a standardized environment, no easy solutions. Isn't reality fun!

"Klatuu" wrote:

> 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.
> >
> > --
> > 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.
> >
> >
> >
.

Relevant Pages

  • Re: Run Time Error
    ... Open a code window. ... Solving Problems with Library References ... Compact the database to get rid of this junk: ... form opens and I can select parameters from every spot except the From ...
    (microsoft.public.access.reports)
  • Re: Main Menu Form Will Not Open
    ... What is the name of the form that should open when the database opens? ... Now that I have converted the database what should the new references be? ... When I opened the code and check the references the Microsoft DAO ...
    (microsoft.public.access.forms)
  • Re: CommonDialog beginners question
    ... References are something you set by clicking the Project menu, ... The first line opens a database before you run the dialog. ... Set MyDB = OpenDatabase ...
    (comp.lang.basic.visual.misc)
  • Re: Main Menu Form Will Not Open
    ... What is the name of the form that should open when the database opens? ... Microsoft can not find the macro "mnuMain" the macro groups don't exist ... Check for the correct references. ...
    (microsoft.public.access.forms)
  • Re: DB Architecture Questions (for joe celko)
    ... So a deck of punch cards or a mag tape is just like an SQL Schema to ... a table has a name in the database. ... OCCURS clause. ... This rule would be enforce by a REFERENCES clause on the Orders table ...
    (microsoft.public.sqlserver.programming)