(Why) Cannot Find msysdb and other 'Missing' References?

[Michael Miller]

I have had some random users, after using the program fine, for months, come
up with either of the above Subject's errors, msysdb and objects showing as
Missing in the References list.

I have been able to resolve both those problems, but I don't know what
causes them (msysdb is corruption, I know, but why?).

Does anyone know the cause of these problems.

Half of our office is located in MN and I am in CT, and the users have their
own front ends, and the back end mdb is located on our shared server. The
server is notoriously slow and MN takes 15 mins to open forms. There is also
a chance that their connection to the server, over bridges and routers,
burps, and maybe they temporarily (seconds) lose their connection, while the
Access app is open. I don't know.

But, wouldn't those errors fix themselves if they get out of Access and go
back in, and especially if they reboot also???

Thanks.

 

[Rick Brandt]

I have had some random users, after using the program fine, for
months, come up with either of the above Subject's errors, msysdb and
objects showing as Missing in the References list.

I have been able to resolve both those problems, but I don't know what
causes them (msysdb is corruption, I know, but why?).

Does anyone know the cause of these problems.

Half of our office is located in MN and I am in CT, and the users
have their own front ends, and the back end mdb is located on our
shared server. The server is notoriously slow and MN takes 15 mins
to open forms. There is also a chance that their connection to the
server, over bridges and routers, burps, and maybe they temporarily
(seconds) lose their connection, while the Access app is open. I
don't know.

But, wouldn't those errors fix themselves if they get out of Access
and go back in, and especially if they reboot also???

Thanks.

Access CANNOT be reliably run as a file share over a WAN connection. The
only practical way to operate over a WAN is with remote control software
like Terminal Services or PCAnywhere.

Keep in mind that the best WAN connection you will ever find is still MUCH
slower and suffers from way more dropped packets than the worst ethernet LAN
you would ever encounter and Access is picky enough running on a LAN.

 

[Michael Miller]

Thanks, Rick.

MichaelM

Access CANNOT be reliably run as a file share over a WAN connection. The
only practical way to operate over a WAN is with remote control software
like Terminal Services or PCAnywhere.

Keep in mind that the best WAN connection you will ever find is still MUCH
slower and suffers from way more dropped packets than the worst ethernet LAN
you would ever encounter and Access is picky enough running on a LAN.