AutoNumber corruption prblem

[Wulff]

Hello,

I just ran into the AutoNumber corruption bug with A2k. Reading the MS
knowledgebase articles on the issue, I understood that this should be fixed
with msjet40 SP4 or later. I checked my version and - surprise - found it to
be SP7. So the AutoNumber problem should not occur - ? Also I found at MS no
hint how to repair the tables. Finally I found Allen Browne's code, which
did the job perfectly (thanks, Allen).

I updated to SP8 as recommended, but I'm not so confident the problem will
stay away in the future, since it hit me with the allegedly fixed SP7. Or is
there another constellation which could cause a sudden occurrence of
duplicate AutoNumbers?

Does anyone have sinilar experiences? I would be happy to know, since I'm
thinking about migrating to at least MDE or another true SQL engine, because
I can't afford being bitten frequently by this bug - my customers won't
appreciate... But OTOH migrating is a lot of work I would like to avoid.

Thanks for any hints..

 

[Tony Toews]

I just ran into the AutoNumber corruption bug with A2k. Reading the MS
knowledgebase articles on the issue, I understood that this should be fixed
with msjet40 SP4 or later. I checked my version and - surprise - found it to
be SP7.

SP7 was known to be buggy. I can't recall if it had the same problem.

I updated to SP8 as recommended, but I'm not so confident the problem will
stay away in the future, since it hit me with the allegedly fixed SP7. Or is
there another constellation which could cause a sudden occurrence of
duplicate AutoNumbers?

Older SPs are the only cause I recall seeing in the newsgroups.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm