Why does that matter? They'll just reinstall the application and a new unique ID will be generated right?
"Aaron Ardiri" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > > If generating a probablistically unique number is the approach you want to take, > > then you might want to do something like gather information from a number of > > sources (current time, current tick count, current user HotSync name, database > > LocalID, a random number from SysRandom, etc.), store all of that data in a > > buffer, and then do a CRC-32 of that buffer. > > then, what happens when someone hard-resets? and has to reinstall > everything - your "uniqueness" has just flown out the window.. this > will be a mega pain in the backside to users :( > > their saved preferences may store the info, but what if this gets > corrupted? or, if the user does a 100% clean reinstall of everything > :)) > > just my 2c :P hotsync username is pretty good on its own. so what if > two "kiddies" want to share the same username :)) they surely wont > be syncing at the same machine :P > > // az > [EMAIL PROTECTED] > http://www.ardiri.com/ <--- free games! > > > -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
