It's getTickCount() that is the culprit...

See: http://www.forta.com/blog/index.cfm?mode=e&entry=886

Courtesy of fullasagoog!

B)

Tim McAuliffe wrote:
Hey Folks,

Just found a little issue with MX 6.1 that wasn't in previous versions...

Try seeding the random number generator like this:

<cfset randomize(gettickcount())>

Thought this was a nice way to use randomize. Alas, it no longer works in
MX 6.1. Not sure if the number that gettickcount() returns is larger or if
randomize() has a lower range of values that it accepts, but either way
it's kaput.

Hope that helps someone...

Tim

---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

MX Downunder AsiaPac DevCon - http://mxdu.com/



--
Brett Payne-Rhodes
Eaglehawk Computing
t: +61 (0)8 9371-0471
f: +61 (0)8 9371-0470
m: +61 (0)414 371 047
e: [EMAIL PROTECTED]
w: www.ehc.net.au


--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]

MX Downunder AsiaPac DevCon - http://mxdu.com/

Reply via email to