M
Mark Burns
We've got a long-standing deployed Access XP application.
Suddenly, we're getting errors on PCs that have been running our db app for
many months, where it seems the reference to the Office XP Web components
DLL is suddenly going MISSING on us on particular PCs.
We've already asked the users the standard "what have you
done/installed/uninstalled since yesterday when this worked just fine"
questions. We've been thinking that perhaps an Windows or Office update
might've been done. No in all cases thus far.
We're coping with this, but it's a hassle to chase everyone off the database
at a location and fix (remove) the suddenly-now-broken reference from the
database (which is OK since we're not using the web components at this
time), but the question remains:
What the HECK is causing these OWC reference to suddenly die on selected
PCs??
Any insights appreciated.
Suddenly, we're getting errors on PCs that have been running our db app for
many months, where it seems the reference to the Office XP Web components
DLL is suddenly going MISSING on us on particular PCs.
We've already asked the users the standard "what have you
done/installed/uninstalled since yesterday when this worked just fine"
questions. We've been thinking that perhaps an Windows or Office update
might've been done. No in all cases thus far.
We're coping with this, but it's a hassle to chase everyone off the database
at a location and fix (remove) the suddenly-now-broken reference from the
database (which is OK since we're not using the web components at this
time), but the question remains:
What the HECK is causing these OWC reference to suddenly die on selected
PCs??
Any insights appreciated.