I'm experiencing duplicate values in autonumber fields (PrimaryKey = True,
Unique = True) in A2002 database. What's going on? How could it happen? To
me it seems as a SUPER BUG which should never leave Microsoft!!!
Grrrrrrrr........

Did MS guys & gals test A2002 before they released it?

:-( :-( :-(

Vlado

On Thu, 24 May 2007 12:42:26 +0200, Vladimír Cvajniga <(E-Mail Removed)> wrote:

>I'm experiencing duplicate values in autonumber fields (PrimaryKey = True,
>Unique = True) in A2002 database. What's going on? How could it happen? To
>me it seems as a SUPER BUG which should never leave Microsoft!!!
>Grrrrrrrr........

This is a confirmed problem if you're using Jet version 4.0.2927.4 and earlier. You need to update to the latest Jet
service pack:

http://support.microsoft.com/kb/291162/EN-US/


>
>Did MS guys & gals test A2002 before they released it?
>
>:-( :-( :-(
>
>Vlado

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

TYVM for your response, Scott.

Same problems in A2003 and A2007, see
http://support.microsoft.com/kb/884185. Microsoft Jet 4.0 Database Engine
Service Pack 8 (SP8) may be one of the reasons that make duplicate
autonumbers appear. AFAIK, SP8 is the latest one...
My version of Msjet40.dll is 4.0.8618.0 (see MS Bulletin MS04-014) which is
higher then SP8 (4.0.8015.0). That's why I think I'm lost, ie. there's no
solution for the duplicate-autonumber-bug at the moment.

BTW, there are different versions of MS Jet 4 SP4 (for different operating
systems). Does A2002 PDW handle Msjet40.dll correctly so that end users
don't have to install latest SP if they have "my" Msjet40.dll or newer?

Vlado

"Scott McDaniel" <scott@NoSpam_Infotrakker.com> píse v diskusním príspevku
news:(E-Mail Removed)...
> On Thu, 24 May 2007 12:42:26 +0200, Vladimír Cvajniga <(E-Mail Removed)>
> wrote:
>
>>I'm experiencing duplicate values in autonumber fields (PrimaryKey = True,
>>Unique = True) in A2002 database. What's going on? How could it happen? To
>>me it seems as a SUPER BUG which should never leave Microsoft!!!
>>Grrrrrrrr........
>
> This is a confirmed problem if you're using Jet version 4.0.2927.4 and
> earlier. You need to update to the latest Jet
> service pack:
>
> http://support.microsoft.com/kb/291162/EN-US/
>
>
>>
>>Did MS guys & gals test A2002 before they released it?
>>
>>:-( :-( :-(
>>
>>Vlado
>
> Scott McDaniel
> scott@takemeout_infotrakker.com
> www.infotrakker.com

P.S. There's wrong link to WindowsXP-KB829558-x86-CSY.exe (Czech version) at
http://support.microsoft.com/kb/239114/. Instead, it points to
windowsxp-kb829558-x86-enu.exe (English version).
My lord... :-( :-( :-(

Vlado

"Vladimír Cvajniga" <(E-Mail Removed)> píse v diskusním príspevku
news:%(E-Mail Removed)...
> TYVM for your response, Scott.
>
> Same problems in A2003 and A2007, see
> http://support.microsoft.com/kb/884185. Microsoft Jet 4.0 Database Engine
> Service Pack 8 (SP8) may be one of the reasons that make duplicate
> autonumbers appear. AFAIK, SP8 is the latest one...
> My version of Msjet40.dll is 4.0.8618.0 (see MS Bulletin MS04-014) which
> is higher then SP8 (4.0.8015.0). That's why I think I'm lost, ie. there's
> no solution for the duplicate-autonumber-bug at the moment.
>
> BTW, there are different versions of MS Jet 4 SP4 (for different operating
> systems). Does A2002 PDW handle Msjet40.dll correctly so that end users
> don't have to install latest SP if they have "my" Msjet40.dll or newer?
>
> Vlado
>
> "Scott McDaniel" <scott@NoSpam_Infotrakker.com> píse v diskusním príspevku
> news:(E-Mail Removed)...
>> On Thu, 24 May 2007 12:42:26 +0200, Vladimír Cvajniga <(E-Mail Removed)>
>> wrote:
>>
>>>I'm experiencing duplicate values in autonumber fields (PrimaryKey =
>>>True,
>>>Unique = True) in A2002 database. What's going on? How could it happen?
>>>To
>>>me it seems as a SUPER BUG which should never leave Microsoft!!!
>>>Grrrrrrrr........
>>
>> This is a confirmed problem if you're using Jet version 4.0.2927.4 and
>> earlier. You need to update to the latest Jet
>> service pack:
>>
>> http://support.microsoft.com/kb/291162/EN-US/
>>
>>
>>>
>>>Did MS guys & gals test A2002 before they released it?
>>>
>>>:-( :-( :-(
>>>
>>>Vlado
>>
>> Scott McDaniel
>> scott@takemeout_infotrakker.com
>> www.infotrakker.com
>

On Thu, 24 May 2007 13:49:02 +0200, Vladimír Cvajniga <(E-Mail Removed)> wrote:

>TYVM for your response, Scott.
>
>Same problems in A2003 and A2007, see
>http://support.microsoft.com/kb/884185. Microsoft Jet 4.0 Database Engine
>Service Pack 8 (SP8) may be one of the reasons that make duplicate
>autonumbers appear. AFAIK, SP8 is the latest one...
>My version of Msjet40.dll is 4.0.8618.0 (see MS Bulletin MS04-014) which is
>higher then SP8 (4.0.8015.0). That's why I think I'm lost, ie. there's no
>solution for the duplicate-autonumber-bug at the moment.

If you're running the latest SP, then perhaps there are some problems with your database. Have you tried importing all
your objects to a new, blank database?

>
>BTW, there are different versions of MS Jet 4 SP4 (for different operating
>systems). Does A2002 PDW handle Msjet40.dll correctly so that end users
>don't have to install latest SP if they have "my" Msjet40.dll or newer?

No. The PDW won't deal with ANY updates unless you include them with the deployment. Typically your installer would
check for the correct version of the file and then either continue or alert the user and (a) install the update, if it's
included with the deployment, (b) launch a browser window so that the user could select the correct update package or
(c) abort the installation and tell the user to update their machine. Of the 3, (a) is the most "clean" but it can
produce huge deployments. (b) is probably the easiest to deal with, since you don't know what OS and SP your enduser
will be running.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

Please note that this is Aar.on Kem.pff pretending to be a reliable poster
to these newsgroups.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Tom Wickerath" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> if your silly database can't do silly autonumbers reliably--- then you
> should be using SQL Server and Access Data Projects
>
>
> "Vladimír Cvajniga" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> I'm experiencing duplicate values in autonumber fields (PrimaryKey =
>> True, Unique = True) in A2002 database. What's going on? How could it
>> happen? To me it seems as a SUPER BUG which should never leave
>> Microsoft!!! Grrrrrrrr........
>>
>> Did MS guys & gals test A2002 before they released it?
>>
>> :-( :-( :-(
>>
>> Vlado
>
>

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.


"Tom Wickerath" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> if your silly database can't do silly autonumbers reliably--- then you
> should be using SQL Server and Access Data Projects
>
>
> "Vladimír Cvajniga" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> I'm experiencing duplicate values in autonumber fields (PrimaryKey =
>> True,

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.


"Tom Wickerath" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> stop blaming everything else but the database format
>
<SNIPPED>
> move to SQL Server and they don't subject you to crap like this
>
>
>
> "Scott McDaniel" <scott@NoSpam_Infotrakker.com> wrote in message
> news:(E-Mail Removed)...
>> On Thu, 24 May 2007 13:49:02 +0200, Vladimír Cvajniga <(E-Mail Removed)>
>> wrote:
>>
>>>TYVM for your response, Scott.

if your silly database can't do silly autonumbers reliably--- then you
should be using SQL Server and Access Data Projects


"Vladimír Cvajniga" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> I'm experiencing duplicate values in autonumber fields (PrimaryKey = True,
> Unique = True) in A2002 database. What's going on? How could it happen? To
> me it seems as a SUPER BUG which should never leave Microsoft!!!
> Grrrrrrrr........
>
> Did MS guys & gals test A2002 before they released it?
>
> :-( :-( :-(
>
> Vlado

stop blaming everything else but the database format

if you use a piece of **** database, you're going to have problems

move to SQL Server and they don't subject you to crap like this



"Scott McDaniel" <scott@NoSpam_Infotrakker.com> wrote in message
news:(E-Mail Removed)...
> On Thu, 24 May 2007 13:49:02 +0200, Vladimír Cvajniga <(E-Mail Removed)>
> wrote:
>
>>TYVM for your response, Scott.
>>
>>Same problems in A2003 and A2007, see
>>http://support.microsoft.com/kb/884185. Microsoft Jet 4.0 Database Engine
>>Service Pack 8 (SP8) may be one of the reasons that make duplicate
>>autonumbers appear. AFAIK, SP8 is the latest one...
>>My version of Msjet40.dll is 4.0.8618.0 (see MS Bulletin MS04-014) which
>>is
>>higher then SP8 (4.0.8015.0). That's why I think I'm lost, ie. there's no
>>solution for the duplicate-autonumber-bug at the moment.
>
> If you're running the latest SP, then perhaps there are some problems with
> your database. Have you tried importing all
> your objects to a new, blank database?
>
>>
>>BTW, there are different versions of MS Jet 4 SP4 (for different operating
>>systems). Does A2002 PDW handle Msjet40.dll correctly so that end users
>>don't have to install latest SP if they have "my" Msjet40.dll or newer?
>
> No. The PDW won't deal with ANY updates unless you include them with the
> deployment. Typically your installer would
> check for the correct version of the file and then either continue or
> alert the user and (a) install the update, if it's
> included with the deployment, (b) launch a browser window so that the user
> could select the correct update package or
> (c) abort the installation and tell the user to update their machine. Of
> the 3, (a) is the most "clean" but it can
> produce huge deployments. (b) is probably the easiest to deal with, since
> you don't know what OS and SP your enduser
> will be running.
>
> Scott McDaniel
> scott@takemeout_infotrakker.com
> www.infotrakker.com