VBA::_ErrObject

Hello.

I've got such a problem. In Visual Basic I have made ActiveX Dll and function like:

Public Sub showError(error as ErrObject)
...
End sub

A this Dll I want to use in VC++
I create IDL file, compile it, generated .c and .h files were added to project a compiled.

But then the function in VC++ looks like:
HRESULT showError(VBA::_ErrObject **error);

And I don't know how to create that VBA::_ErrObject in VC++.
It look like it is a normal COM object (_ErrObject) but _ErrObjectPtr.CreateInstance doesn't work.

I have #import msvbvm60.dll used.

Thanks for help.

hanzelkoAsked:
Who is Participating?
 
_ys_Commented:
> But Set objError = new ErrObject doesn't work.
I'd already suggested it wouldn't. My comment was ambiguous.

> It looks like the objError is the same global err object
It is. Atfer all it is global static declared.

There's special restrictions put on the VB ErrObject - a discussion of which is better suited to the VB area. VB does reset this at regular intervals, so you cannot wholly guarantee it's contents from one function to function.

If you truly want to persist it's value, and govern its contents, I suggest you roll out your own pseudo-ErrObject. I've had to do this before within VB itself, never mind interoperating with C++, so I know it's a pain in the ar$e.
0
 
_ys_Commented:
Within VB ErrObject is non-creatable. It's static. Try making:
Set objError = New ErrObject
work.

Expose a GetErrObject from your VB ActiveX DLL and use it to obtain a pointer to ErrObject from VC++. At least you'll get an ErrObject pointer which you can pass to showError.
0
 
hanzelkoAuthor Commented:
Hi.

I have tried it.
But Set objError = new ErrObject doesn't work.
It throws exception ActiveX cant create object in VB.

So I have used
Set objError = err     // return global error object.

This works, but behaves buggy. Something in objErrr is set when I call showError but description is not set.
It looks like the objError is the same global err object and objErr.descritption is empty.

So where can be problem.
0
 
hanzelkoAuthor Commented:
Ok thanks a lot. I have though about it the same way. pseudoErrObject will be good.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.