MVPs: Autonumber bug; how meek can we be?

  • Thread starter Thread starter kiln
  • Start date Start date
K

kiln

This is the third post I've made on this topic over the last several
months. Access 2000 has a catastrophic autonumber bug. It's well
documented, and completely unfixed by Microsoft. I can hardly believe
how little discussion this has received in the newsgroups. There has
been no response from Microsoft at all.

I am now asking for the Access MVPs to address this issue. I know that
your MVP status is honorary and that you don't have any official voice
at Microsoft. But why aren't any of you kicking up a fuss over this?
This is the worst bug I've ever seen in Access. Duplicate primary keys -
how low can you go?

Maybe none of you take Access/Jet seriously anymore? That is the only
conclusion I can draw. Microsoft obviously doesn't either, and has no
reason to, since apparently both MVPs and bulk of Access developers are
willing to put up with the most ruinous bugs in silence.
 
kiln said:
This is the third post I've made on this topic over the last several
months. Access 2000 has a catastrophic autonumber bug. It's well
documented, and completely unfixed by Microsoft. I can hardly believe
how little discussion this has received in the newsgroups. There has
been no response from Microsoft at all.
Click to expand...

I'm new here so please forgive my ignorance. I have not heard of this issue
before, do you have a link or article I can referr to in order to read up on
this issue??

Thanks,

Jeff
 
Hi Douglass

I started a thread on Oct 4 called "Devastating Autonumber bug in Access
2000" that details my setup. I'm at Win2k sp4 and Jet sp7. It's not
fixed and that is part of what is so spooky about the level of
attention, or the grade of programmers that MS is throwing at problems
with Access. First there was no problem with Autonumbers. Then they get
the bright idea to have a seed value (I guess). Then they blow the
implementation. Then they issue a patch that they claim fixes it, but
doesn't. That's sloppy in the extreme.
 
Hi Jeff

Take a look at two recent threads

"Devastating Autonumber bug in Access 2000" on Oct 4
(microsoft.public.access.formscoding,microsoft.public.access.modulesdaov
ba,microsoft.public.access.tablesdbdesign)

and

"AutoNumber uses less than greatest value!" on Sept 9
(microsoft.public.access.tablesdbdesign only I think)
 
Kiln, we can understand your frustration with a problem that was introduced
in Access 2000 as part of the change to Jet 4.

However, there are some aspects to bear in mind:

1. If the autonumber is the primary key, if does not function correctly, but
you do not get the duplicates. The result is a frustration in data entry
rather than a compromise of existing data.

2. Personally, I have not seen the issue resurface since the Jet SP7 patch.
That's why I'm not "kicking up a fuss".

3. If you can generate a reproducable scenario under Jet SP7, please take it
up with support.microsoft.com. A small file and the exact steps to reproduce
the issue would be most helpful for them.
 
Hi Allen

I have created a set of data files that repro this behavior. I've
submitted a report to MS but who knows how long it will take them to
respond, if ever. The submission form has no way to submit the test
files.

As far as your first point goes, the autonumber is a PK and does indeed
attempt to create a duplicate value. The only way I'm able to get my
users back to work is by applying your patch each time we do a beta test
iteration.

(http://allenbrowne.com/ser-40.html)

Sure if making everyone feel "great" about Access.
 
Back
Top