>>>Thanks Gary. The .TLB file is there. It resides in the same directory as the .DLL. Am I missing something else?
>>
>>I'm not sure. I was thinking the TLB file only because I had the same message recently when transfering a COM server to another machine and forgot the TLB file. I spent almost a day before remembering the TLB. I have had problems with this error or a similar one when machines had differnt language settings, e.g., an exe loads fine under American English but chokes under UK English. I'm sure that isn't your problem, I assume all your machines are set to UK English. Sorry, out of ideas.
>>
>>Gary Foster
>>Pointsource Consulting Inc.
>
>Gary,
>
>After doing exactly what you did, that is sit around for a day, a colleague's friend mailed him to ask me to check the machine locales. That was the problem! It seems that when VFP generates the TLB it writes the machine locale into the GUID causing this problem. It seems we have to modify the GUID for a 'language neutral' setting. Did you manage to change the GUID? Microsoft is, I believe, aware of this problem and has a fix. I don't have the URL, however, if you're interested, I could mail you the fix (which does'nt guarantee a fix!) which was mailed to be by my colleague's friend.
>
>Thanks for your help

Sanjay,
Yeah, I would like a possible fix if you have one. The possibility that VFP compiled some locale info into the exe would never have occured to me.

Thanks.

Gary