David,

>When you build the MTDLL on different computers you MAY get a different CLSID. If you copy the entire project to another computer AFTER it has first been built as a COM server on the first computer, the CLSID's will be the same because the CLSID is stored in the PJX.

Thanks for that additional info.. we'd been having problems deploying our COMs onto our webservers for quite awhile before I found that the errors only occurred when a different developer built it the next time. And that was caused by the differing CLSID's.

I think though there is a problem with projects passed around via VSS PJMs because I've seen problems in reading the PJM onto a new machine when the CLSIDs were in the file. I had to strip tohose lines out of the PJM before I could get VFP to successfully join the project.

>However, even then, you can override that and create a different CLSID any time you want by checking "Regenerate Component IDs" on the Build dialog. Generally it's a good idea to stick with the same CLSID unless you have some special circumstance, because you can sometimes end up with multiple entries in the registry with several CLSIDs attached to the same "project.class" component name.