Refference Confusion - Please help!

  • Thread starter Thread starter John
  • Start date Start date
J

John

Can someone please tell me how I can avoid the following problem.

I develop a database on a machine at home and deliver it to a my office with
8 networked computers. I develop in Access2000 on WinME at home but the
office users all have OfficeXP (Access2002)
Some on WinXP some on Win2000.
I have a refference to the "Jet & Replication Object 2.6 Library" on My
Computer at home.
When I deliver my Front End to the office computers, all the Win2000
computers have a broken reffence to this library wich is the msjro.dll
I have to reset the refference to "Jet & Replication Object 2.5 Library", a
lower version.
The users have updated the "Office XP to Service Pack 3"
My confusion is that MY OLDER Version of Access has the Later Version of
the Jet & Replication Library.
Am I able to simply copy the msjro.dll form a WinXP computer or My home
Computer to these Win2000 Computers. If not, how do I get the latest version
of msjro.dll
Regards
Brad
 
This is a case for Front/Back End where the Front End is installed on each of
the workstations & the Back End on a shared drive. If you do this the Front
End should be developed in the early version of Access as the later versions
of Access will automatically update the reference. The down side is that each
update (of the Front End) must be distributed to each workstation (although
this can be automated if there are a lot of workstations). I have used this
setup on a number of networks quite successfully.
Be warned, though, that you must develop in the early version of Access, in
your case A2K, otherwise you will have to manually update the references on
those workstations with A2K
HTH
Terry
 
Hi Terry,
The Scenario you describe is exactly what I am doing.
Thats why I am so confused.
I develop on a machine with WinME & Office2000
And deliver to machines with Win2000 & WinXP
that are all using OfficeXP ServicePack 3.
All 8 machines have the FrontEnd and the server
has the BackEnd
ALL workstations are using a version of Office
higher than the one I develop under

I don't understand why my Win2000 machines are having
the problem described.
 
Hi Douglas,

Now I'm even more confused....
I just downloaded and installed MDAC 2.8 on my
Home System that runs WinME & Office2000

Now when I go to set a refference to the Jet & Replication object library
it's the 2.5 library NOT the 2.6 which is what I had before.
Any Idea as to whats going on?

Thanks
 
Sorry, I don't have an answer for you.

Try poking around the DLL Help database
http://support.microsoft.com/dllhelp/ to see whether you can determine where
your desired version of msjro.dll can come from, but be aware that the
database isn't 100% complete (and it looks as though they're having problems
with data appearing multiple times)
 
Hi Douglas,
It turns out that when I am viewing the Refference,
in the Refference Window it shows up as
Jet & Replication Object 2.5 Library.
But if I select it, then close & re-open the window
it shows as 2.6
Go figure...
Anyway I guess I can istall the MDAC 2.8 at the Office as well.
Thanks for your input...
both here and re the Autonumber clarification in another thread.
 
I missed the fact that your home computer has the LATER version of the DLL
(apology). This is the gotcha. You could try copying the DLL from your home
computer and manually registering it on the work computers. This would
probably work if the DLL does not have dependancies. The installation of MDAC
2.8 at work may be the best bet.
Keeping updated is great, provided everybody does it.
 
John said:
I have a refference to the "Jet & Replication Object 2.6 Library" on My
Computer at home.
Click to expand...

Do you even need that reference?

Do you have any references besides the basic four? Are you sure you
need them? Write down the path and name of the extra ones, delete
from the references list and Compile and Save All. Keep any
necessary references and ensure they are distributed to the target
system.

For a very detailed page on reference problems see
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

The Access 2000 default references are:
Visual Basic for Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library
or
Microsoft DAO 3.6 Object Library

The Access 2002 default references when the MDB is created in Access
2000 format are:
Visual Basic for Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library

The Access 2002 default references when the MDB is created in Access
2002 format are:
Visual Basic for Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.5 Library.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Thanks for the info Tony,
And yes i need the refference for my program.
I have a DB Maintenance Form that allows for
compacting, linking and backing up.
I'll try installing the mdac 2.8 on the office comuters this coming week.
Thanks again for the info.
Brad
 
And yes i need the refference for my program.
I have a DB Maintenance Form that allows for
compacting, linking and backing up.
Click to expand...

Why? What does that reference give you when other methods would also
work?

Relink Access tables from code
http://www.mvps.org/access/tables/tbl0009.htm

DBEngine.CompactDatabase olddb, newdb, locale, options, password

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Hi Terry
Terry said:
I missed the fact that your home computer has the LATER version of the DLL
(apology). This is the gotcha. You could try copying the DLL from your home
computer and manually registering it on the work computers. This would
probably work if the DLL does not have dependancies. The installation of MDAC
2.8 at work may be the best bet.
Keeping updated is great, provided everybody does it.
Click to expand...
 
Back
Top