L
luv2bike2
I have a db (Access 2003) that several users use, it is located on my file
server. My users use a shortcut to get to it. about a month ago, my network
was upgraded (new servers and domain change). Everything was working fine
before the upgrade. The access databases were moved (copied, I don't know,
it was all done by consultants) over to the new file server. Now users who
have Windows 2000 can open up the database however they can not do anything
because they get a pop up that says:
"Your WO Tracking Database or project contains a missing or broken reference
to the file "msjro.dll" version 2.6
To ensure that your database or project works properly, you must fix this
reference"
Users who have Windows XP have no problem.
On the users computer i deleted the shortcut. On the users computer i went
directly to the file located on the file server and opened up the db from
there and still received the error message on the users computer. This is
happening on Windows 2000 SP4 computers.
If I login as the user into that DB from my computer (which is XP SP3) I do
not get that error message.
What do I need to do to get this working for the users who have windows 2000
SP4?
server. My users use a shortcut to get to it. about a month ago, my network
was upgraded (new servers and domain change). Everything was working fine
before the upgrade. The access databases were moved (copied, I don't know,
it was all done by consultants) over to the new file server. Now users who
have Windows 2000 can open up the database however they can not do anything
because they get a pop up that says:
"Your WO Tracking Database or project contains a missing or broken reference
to the file "msjro.dll" version 2.6
To ensure that your database or project works properly, you must fix this
reference"
Users who have Windows XP have no problem.
On the users computer i deleted the shortcut. On the users computer i went
directly to the file located on the file server and opened up the db from
there and still received the error message on the users computer. This is
happening on Windows 2000 SP4 computers.
If I login as the user into that DB from my computer (which is XP SP3) I do
not get that error message.
What do I need to do to get this working for the users who have windows 2000
SP4?