AnsweredAssumed Answered

vrf ActiveX problem

Question asked by VRFuser on Oct 12, 2005

Like • Show 0 Likes0
Comment • 3

I'm sure that the variable is of the right type. I've done the same
program with VB .NET and it works perfectly.
The variable is a WinEASY_RemoteCtrl.Application object and OpenWsp is
a member of this class.
When I create the application object with VB .NET I've to write this code

on error resume next
set WEapp = CreatoObject("WinEASY_RemoteCtrl.Application")
on error goto 0

Do you think that I've to change the error processing in VEE as well
(if there is a way)?

Thanks.
Michele.

---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".

No one else has this question

Outcomes

3 Replies

VRFuser Oct 11, 2005 5:48 PM
Mark Correct
Correct Answer
> It looks like the application variable isn't correctly initialized,

Or maybe it gets initialized to the wrong thing? Double click a line
carrying WEapp or get var info when the program dies (since it's declared)
and make sure it's the correct object.
-SHAWN-

---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Like • Show 0 Likes0
Actions
VRFuser Oct 11, 2005 7:17 PM
Mark Correct
Correct Answer
Hello VRF,

I've a problem controlling an application with ActiveX in VEE 7.5 (and
7.0 as well) . I've attached a couple of pics illustrating the
situation.
If I create the object like in "Works.jpg" all seem to work properly.
In this case i just pass the application variable from a formula to
the another, without using a global variable.
Instead, if I create an application variable and use it in the program
(see "NotWorks.jpg") the software doesn't work. I can just open the
application but after it looks like i lose the control of it. When i
try to open a workspace (formula WEapp.OpenWsp(sWsp)) I get the
error:

Execution of method "openWsp" in the referenced active X object failed.
Error: 552
System error code: 0x80020003
System error message: Memeber not found

It looks like the application variable isn't correctly initialized,
but I tried every way to initialize it without success. I need to
declare and initialize this variable because a have to handle events
associated with it.

Anyone has had this kind of problem before?

Cheers.

Michele Gobbi.
AIMS (INT) Ltd.
+44 0131 331 7326

---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Like • Show 0 Likes0
Actions
VRFuser Oct 11, 2005 8:00 PM
Mark Correct
Correct Answer
> The variable is a WinEASY_RemoteCtrl.Application
> object and OpenWsp is a member of this class.

Interesting. In spite of looking around for a while I can't find a decent
explanation of what this actually is. I quit after I found a Scientology
reference that mentions WinEASY

At any rate, I *have* actually seen this problem before. It was with the
TestVT example, and the problem was I messed up the class. Had nothing at
all to do with VEE.

> When I create the application object with VB .NET I've to write this code
> on error resume next
> set WEapp = CreatoObject("WinEASY_RemoteCtrl.Application")
> on error goto 0

You mean it doesn't work unless you ignore errors
May I paraphrase Hank Hill? "That library ain't right".

> Do you think that I've to change
> the error processing in VEE as well
> (if there is a way)?

No reason to, and as far as I know can't be done anyway. Dump WinEASY.

Just for spurious info, the problem I had was passing a ByRef Variant to an
Automation library:

Public Function ReportVT(ByRef var As Variant) As Boolean
Dim iVt As Integer
Dim sVt As String

' This *must* be here or this call doesn't work from *any* language.
On Error Resume Next

The problem without ignoring errors was exactly the same: member not found.
It may be that something of the same kind is going on here. I have
absolutely no idea what the problem *really* is, but it has nothing to do
with a member function not being found (in my case anyway).

It may be that the host language is trying to access a member of an incoming
parameter that doesn't exist, or who knows? That's the trouble with
libraries: you didn't write it, you don't know. VB is a hard case too. It
does compile to executable code, but it's not the same as compiling C. The
code executes in an artificial environment that doesn't expose some of it's
weaknesses.

For instance, you can't do SDK multithreading in VB. Oh sure, you'll find
lots of articles that claim you can but they have all sorts of caveats
attached. Plain & simple, it can't *really* be done. If any VB thread
created with CreateThread calls any user32 function, BOOM! If you want to
multithreading in VB then you have to stick with COM or your in a world of
never ending debugging.
-SHAWN-

---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Like • Show 0 Likes0
Actions

vrf ActiveX problem

Outcomes

Related Content

Recommended Content