>>>>I'd like to know the answer to this too, but unfortunately, I think we're SOL. This bites users of my public domain tools from time to time...
>>>
>>>Hey Erik,
>>>
>>>Ug, I was afraid of that. I guess I'll just prefix the class libraries some incredibly obscure name that hopefuly nobody else would use.
>>
>>That's what I _should_ do for public domain tools, but the libraries I use in them, I use everywhere.
>>
>>
>>> SillyCatBananasAreForMonkeys_base.vcx should be pretty safe huh? <g>
>>
>>You'd think so, but I have a library called exactly that. Better make it piglatin, or use extended characters in the name. ½abanana.vcx for example.
>
>You can use GUID also

No, too much likelyhood of duplicate GUIDs. It has been shown using tools written on the IMPS (Infinite Monkey Protocol Suite) that enough monkeys will eventually come up with the same GUID.

You're gonna have to use something that they can't type with the keyboard. Perhaps a filename with an odor attached or something. Of course you'd have to have a smell-o-vision compatible monitor to open it.