[AccessD] Autonumber in replication

This is exactly the reason why autonumbers should *not* be seen by the
public.

They should be used to uniquelty identify records for relationships -
nothing more.

If a public (case) number is required then it should be created manually.

Cheers,
Andrew

-----Original Message-----
From: Don Elliker [mailto:delliker at hotmail.com]
Sent: Thursday, 14 August 2003 5:33 AM
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

IMPORTANT - PLEASE READ ******************** 
This email and any files transmitted with it are confidential and may 
contain information protected by law from disclosure. 
If you have received this message in error, please notify the sender 
immediately and delete this email from your system. 
No warranty is given that this email or files, if attached to this 
email, are free from computer viruses or other defects. They 
are provided on the basis the user assumes all responsibility for 
loss, damage or consequence resulting directly or indirectly from 
their use, whether caused by the negligence of the sender or not.