L
Louise54
In late summer of 2008 I posted a question regarding a corruption issue we
were having with our split database. Data resides in an Access 2.0 database
on our server; forms, reports, etc. are on local drive of approx 12 users
workstaitions, using different versions of Access (most 2003, two 2007).
Someone pointed me to a security update Microsoft shipped in late May
(MS08-028/KB950749) and sure enough, once we installed the hotfix KB954193
the problem disappeared.... for a while. At the time we installed the hotfix,
we also turned off Auto Updates to monitor which updates occurred.
The same problem has just recently started up again. We've checked every
workstation multiple times, but can't find that any are getting updates we
don't know about.
I can't seem to find the original thread to this problem, but it was titled
"Corruption Problem with 2.0â€" in this forum.
Any help on what may be causing this reoccurence would be greatly
appreciated. We are trying to hang in with our 2.0 until we convert to SQL
Server in the Fall of 2009.
Thanks so much ahead for any suggestions/help.
-Louise
were having with our split database. Data resides in an Access 2.0 database
on our server; forms, reports, etc. are on local drive of approx 12 users
workstaitions, using different versions of Access (most 2003, two 2007).
Someone pointed me to a security update Microsoft shipped in late May
(MS08-028/KB950749) and sure enough, once we installed the hotfix KB954193
the problem disappeared.... for a while. At the time we installed the hotfix,
we also turned off Auto Updates to monitor which updates occurred.
The same problem has just recently started up again. We've checked every
workstation multiple times, but can't find that any are getting updates we
don't know about.
I can't seem to find the original thread to this problem, but it was titled
"Corruption Problem with 2.0â€" in this forum.
Any help on what may be causing this reoccurence would be greatly
appreciated. We are trying to hang in with our 2.0 until we convert to SQL
Server in the Fall of 2009.
Thanks so much ahead for any suggestions/help.
-Louise