|
-
Mar 18th, 2001, 11:22 PM
#1
Thread Starter
New Member
I have a COM object that will cause a Visual C (VC) compiled DLL. However, after updating that VC DLL, the COM object no longer find that DLL on Win NT/2000. I have tried re-compiling the VB COM object or unreg. and then reg. the COM object again.
What is the real causes and how to sort out the problem.
Pls. advice me asap.
-
Mar 19th, 2001, 05:44 AM
#2
Hyperactive Member
Are you changing you guid when you recompile the VC side. How is your ref to the COM object done in vb (early bound, late bound with createobject etc).
td.
"One logical slip and an entire scientific edifice comes tumbling down." - Robert M. Pirsig
[email protected]
"but if Einstein is right and God is in the details, reality requires that we sometimes get religion." - Scott Meyers.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|