[AccessD] Autonumber in replication

The autonumber is changed to random because the GUIDs will be assigned
in no given order because the GUID is based on the machine it is created
on.  You wouldn't want to use that as your visible case number, but if
you work with replication, you'll work with GUIDs, whether you see them
or not.  If you use an alternative scheme, you'll have to allow for all
possible circumstances yourself.

Charlotte Foust

-----Original Message-----
From: Don Elliker [mailto:delliker at hotmail.com] 
Sent: Wednesday, August 13, 2003 12:03 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Autonumber in replication


Yes. I just found some info on this in the 2K/ADH - Vol2 page 472. Looks

like a custom assignment of this value is in the wings as JET changes
the 
assignment from sequential to random. Not good for my purposes....I can
just 
see my users face when their new test case is number 1,956,000,045. Come
to 
think of it, I WOULD like to see their face...And don't yell at me about

using autonumber in a visible way,etc. etc....I didn't do that part, it
was 
already like that when I got here..(yeah, sure it was buddy)...anywho, 
thanks
_d



"Things are only free to the extent that you don't pay for them".-Don 
Elliker





>From: "Charlotte Foust" <cfoust at infostatsystems.com>
>Reply-To: Access Developers discussion and problem
>solving<accessd at databaseadvisors.com>
>To: "Access Developers discussion and problem 
>solving"<accessd at databaseadvisors.com>
>Subject: RE: [AccessD] Autonumber in replication
>Date: Wed, 13 Aug 2003 12:48:18 -0700
>
>The only sure way is to make the autonumber a GUID, which you do by 
>selecting Replication ID from the FieldSize property.  It's a bit more 
>complicated to work with GUIDs though because you can't just compare 
>them to each other.
>
>Charlotte Foust
>
>-----Original Message-----
>From: Don Elliker [mailto:delliker at hotmail.com]
>Sent: Wednesday, August 13, 2003 11:42 AM
>To: accessd at databaseadvisors.com
>Subject: [AccessD] Autonumber in replication
>
>
>How do you all handle autonumber fields in replicated database schemas,

>so that the autonumber remains unique? I have this as a pending issue 
>where a
>database tool is potentailly being rolled out to more users than a
>single BE
>/multi FE setup would be good for. I have the primary key on the main
>driver
>table set up as autonumber and I am trying to get my head around this
>concept as applied to replicated db.
>_d
>
>
>"Things are only free to the extent that you don't pay for them".-Don 
>Elliker
>
>_________________________________________________________________
>The new MSN 8: smart spam protection and 2 months FREE* 
>http://join.msn.com/?page=features/junkmail
>
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com 
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com 
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com 
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com