|
-
Jul 21st, 2005, 05:31 PM
#1
Thread Starter
New Member
how do I raise COM errors between ActiveX dlls
My history is more of a C++ developer, so I may be missing something obviouse, but I cannot seem to find a method to raise an actual COM error. This would be similar to a C++ AtlReportError (or something like that). The Err.Raise is simlpy a VB runtime error that does not marshall an error across com.
My situation... I've got a ActiveX dll (library) called from an ActiveX exe. My dll is causing an ADO error to be raised that I want to pass on to the activeX to relay onto the main application for logging, etc. I had a method using events where I call RaiseEvent... and capture that in the client (exe) and set a global object that the calling procedure can call after calling the library function. However, it just seems there should be some better way to raise a COM error from VB natively.
thanks,
Eric
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
|