Hello Lester,

LC> Just to clarify this.
LC> GUID is a Microsoft 'standard' and is required where certain Microsoft
LC> operations are carried out.
LC> UUID is different to GUID, and while it IS more compact, it can not be
LC> used interchangeably as a GUID ( as I understand it ) as it does not use
LC> the same rules for creating it.
Yes, you're right: is't not safe to covert between formats. Here are
results that I have with uuidlib:
-----
uuid_create:
0okI49K!KxcV5OXkrinWuA
uuid_to_guid:
eece2e8c-8f0d-11da-a2bd-b4c1418b5805
guid_to_uuid:
0okI49K!KxcV5OzzzinWuA
uuid_to_guid:
eece2e8c-ffff-11da-a2bd-b4c1418b5805
-----

LC> a GUID layout. So some security checks will flag problems with a UUID or
LC> GUID if it does not match the machine ID that it is flagged as being
LC> generated by. Not a problem to 99.9% of users but we always seem to hit
LC> that 0.1% more often ....
It seems the probability of problems with converting is much higher :)


--
Best regards,
Pavel Menshchikov
http://www.ls-software.com