I'll throw my 2 cents in on the side of GUIDs for replication, INTs otherwise, but here's something to note: if you're generating lists with 100's of rows, using GUIDs exclusively can substantially increase the weight of your generated html. That's typically not an issue for developers, but it could be for your users if they're on slow connections.
For tables you need to be able to replicate, consider having two candidate keys, a GUID and an INT. (Which one is the physical PK is dependent on how easily you need to replicate references to the table.) When generating html, use the INT instead of the GUID. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at [EMAIL PROTECTED]
