Re: Vista - WinXP environment and database corruption?



I have read with total amazement that if an Access2000, 2002, 2003 &
2007 application connects to a database on a computer running Vista
and then another second Vista PC on the network links into the
database it will become corrupted. The corruption is apparently so bad
that the contents of every record in every table are replaced with
#Name? ....brilliant! How on earth can this happen? I could
understand it if a third party database corrupted but an Access
database, well it's totally unbelievable, incompetent even. If I
hadn't read it on Allen Browne's website (which I did whilst looking
for something else) I wouldn't believe it. A complete disaster in the
making, how on earth didn't this show up in testing? This means that
unless fixed Access is single user only. How could an end user manage
this? Most of them can't do attachments. They wouldn't know until
their data was destroyed, it's a nightmare!

William- Hide quoted text -

William, I agree wholeheartedly with your comments. How could this
have not been picked up in testing? As mentioned above, there is a
hotfix available, but that is only useful if the user/client applies
it. The question that comes to mind is: Has this hotfix been applied
as part of Windows Update or is it incumbent on the user to (a) know
that the problem exists, (b) know that a hotfix exists, (c) submit the
required online request to obtain the hotfix (d) manually apply the
hotfix?

If the latter is the case, I believe that it is negligence on MSs part
in the extreme. Another question that comes to mind is : Why have
they made it more difficult than it needs to be to obtain the hotfix?
Instead of just downloading it, one must first submit an online
request.

Perhaps other forum contributors who are closer to MS may know if the
hotfix is being applied through Windows Update. This seems to be the
only way of being reasonably sure that the patch is applied.

.



Relevant Pages

  • RE: Backup Failures
    ... I tracked the source of the error to a new database installed ... Apparently VSS cannot backup an SQL ... > I understand that you need the hotfix KB828481 for a VSS issue. ... > call into the appropriate Microsoft Support phone line, ...
    (microsoft.public.windows.server.sbs)
  • Re: office assistant error
    ... There is a hotfix available to correct the error: ... Is there a way, maybe in the startup code of the database, to stop this ... For information, we use Excel 2000 and Word 2000, and Access 2003. ...
    (microsoft.public.office.misc)
  • Re: Importing table from text file to Access...
    ... I'm a little surprised you got the hotfix because the description you ... before the wizard opens? ... >importing any file, but tables from another database. ...
    (microsoft.public.access.externaldata)
  • Re: Run-time error 3027
    ... If it has then you will want to apply the HotFix that corrects many of the ... Could you please help me with Error 3027 in Access 2000 database? ... Dim RFQNUM As Long ... Dim ZRPOSET As Recordset ...
    (microsoft.public.access.forms)
  • Re: ERROR 467 in Directory Service Event Viewer
    ... unschedued reboots / power outages, crashes by LSAS are possible sources of ... Process ID or PID of the server that owns the DB that was corrupted ... All an all it seems that there is a corruption in Active Directory ... I've contacted MS and they provided a hotfix based on KB article 902396. ...
    (microsoft.public.windows.server.sbs)