>> SYS(2015)is guaranteed to be unique within the same PC.
>
>Are you sure about that? This would require (inter-process) communication between all instances of Fox runtimes on a machine. There seems to be such communication of sorts - a busy Fox can keep other Foxen from closing for a while - but I don't think that IPC is involved in SYS(2015).
What IPC is? I meant the same computer.
>
>> AFAIK, nobody proved otherwise yet.
>
>Might be a nice Sunday morning exercise. Should be easy enough to prove what's up one way or another. *g*
Already proven one way. :)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_foxhelp/html/lngsyslp2015rp___unique_procedure_name.asp"The name that SYS(2015) returns is created from the system date and system time. Calling SYS(2015) more than once during the same millisecond interval will return a unique character string."For all intents and purposes it is unique (again, within the same computer).
Unless somebody is able to prove otherwise. :)
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison