Re: Access 2000 Autonumber Corruption

From: Brendan Reynolds (brenreyn)
Date: 01/13/05 

Date: Thu, 13 Jan 2005 16:35:27 -0000

The latest Jet update should fix it. There are different versions of the
update for different versions of Windows, so the easiest solution, if
possible, is to get each of the users to visit the Windows Update site and
check for updates. Do not rely on MDAC for this - it hasn't included the Jet
components for quite some time now. 

-- 
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com
The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.
"Jim Rodgers" <JimRodgers@discussions.microsoft.com> wrote in message 
news:D5621CF0-C671-425B-9D0F-379D78D60330@microsoft.com...
> I've been using MDB files for things like this for nearly a decade.  But 
> this
> is something new - and quite troublesome.
>
> I have a small workgroup application written in VB6 using ADO where the 
> mdb
> file is on a WinXP/Pro and the clients once were all Win98SE.  Everybody 
> had
> MDAC 2.8 and every other update I could think of.  Things were mostly 
> good.
>
> Then XP/SP2 comes along, and to confuse matters completely, one of my 
> W98SE
> client machines is replaced with XP/Pro/SP2 right when the server was also
> updated to SP2.  Then another, and then one more is upgraded to XP/Home.
>
> "About" the same time as these changes were made, I started getting
> corruption of the autonumber primary key field in one of the tables.
>
> It always happens in the same table.  It is possible that it only happens
> when the XP/Pro client is using the application, but this also might not 
> be
> true.  It's hard to tell with these particular users because they don't
> always report the problem promptly (because they think it's their fault 
> and
> they don't want to get in trouble).
>
> The corruption is this:  the autonumber field rollsback to an already used
> value, thus causing prinary key errors on subsequent .AddNew/.Update
> attempts.  It's the damnedest thing!
>
> Repair or Repair/Compact (either from Access 2000 or through VB6 using 
> JRO)
> does not fix the corruption.  One must copy the data to a new table, 
> delete
> the old one, and rename, etc.
>
> I am using ADO transactions around each critical step in the procedure 
> where
> corruption occurs.  The .BeginTrans and .CommitTrans/.RollbackTrans 
> "pairs"
> are well-understood: I don't believe I have any sneak paths here.  It is
> POSSIBLE that the corruption occurs only subsequent to a .Rollback from 
> the
> XP client, but this is not certain and may be a red herring.
>
> Typically, there is only one user running this procedure at any time, and
> the problem is known to occur when this is the case.
>
> ********* HHHeeeeeeeeelllllllllppppp! *********
>
> - Jim
>
> -- 
> James W. (Jim) Rodgers, P.E.
> Senior Consultant
> General Consulting Engineers, LLC
> Atlanta, GA

Relevant Pages

  • Re: Terminating Application
    ... In one of the greater disasters I was involved in, and had to fix at great expense, ... Windows by changing it to ExitWindowswhich exited ... The disasters you describe ensued. ... went back to my client and we ditched the product. ...
    (microsoft.public.vc.mfc)
  • L2TP/IPSec certificate problem on Windows XP client
    ... We are unable to use a Windows XP VPN client to access a Windows 2000 ... The client machine certificate was issued through automatic ... In an attempt to fix this problem we have reissued ...
    (microsoft.public.win2000.security)
  • Re: Reconnecting Remote Desktop on XP Pro
    ... With the new Windows Mobile 2003 OS there is a reconnect bug in the built-in TSC... ... > The other fix was to go to the system console and log in (and ... > stream and has disconnected the client. ... > The RDP protocol component WD detected an error in the protocol stream ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: System will not Boot
    ... I don't know about a "quick fix" for the registry corruption error, ... Microsoft MVP - Windows Shell/User ... > As he lives 200 km from me, I am having to try and fix this via phone, so ...
    (microsoft.public.windowsxp.general)
  • RE: Problems with corrupt DB and ESEUTIL
    ... I had a client that had a similar problem. ... microsoft. ... That is what they used to fix the problem. ... > know when this corruption began and at this point I'm starting to think maybe ...
    (microsoft.public.exchange2000.information.store)