AnsweredAssumed Answered

Problem with integration of VEE objects into VB

Question asked by tejas.dave on Apr 10, 2010
Latest reply on Apr 14, 2010 by UndeadBob

Like • Show 0 Likes0
Comment • 7

Hi,

    I working on integration of VEE user function into Visual Basic taking reference of Callable AciveX Automation Server in Microsoft Visual Studio 2008. I first tried with very simple example and i called it from Visual basic code and it worked fine. But when i introduced some .NET code into that example. It works fine in VEE Pro. But when i called it from visual basic it failed.

   It gives me error saying "ComException was unhandled", cannot access .NET object to perform operations. VEE Error No: 754 at line where i am calling that function. One more error saying "Could not resolve COM reference "36f6e2f6-a9ce-11d4-98e5-00108301cb39" version 1.0. The type library importer encountered an error during type verification. Try importing without class members." VB code is as follow:

I have attached snap shot of error message, which i got in MS visual studio 2008.

Public Class Form1
    Dim server As New CallableVEE.CallServer
    Dim library As CallableVEE.Library
    Dim calcUF As CallableVEE.UserFunction
    Dim libfile As String

    Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        libfile = "C:\SDA_VEE_Control\Var_Calc.vee"
        server = CreateObject("CallableVEE.CallServer")
        library = server.Libraries.Load(libfile)
        calcUF = library.UserFunctions("Calc")
        calcUF.Call()      '----------------------------- Errored Line
    End Sub

End Class

I suspect it has to do with COM and .Net interoperability. Can anyone tell me how to resolve this problem or require more infomation on it. Thanks in advance.

No one else has this question

Outcomes

UndeadBob Apr 12, 2010 6:17 AM

Not having the VEE code, my first guess is regarding VEE's initialization of variables.

Could not resolve COM reference

Sounds like VEE is trying to call a variable that hasn't been initialized, or is otherwise used improperly.

Actions

tejas.dave Apr 12, 2010 8:30 AM

Hi,

Thanks for your reply.

VEE code (with .Net in it) worked fine in VEE Pro 8.5. But When I called it from Visual basic it didnt work. I have given reference of Callable AciveX
Automation server and .Net assembly (in my case, System.Windows.Forms) in MS Visual Studio 2008 project. So I think there is no problem with initilization
of variables. Please tell me how do i attach VEE code or doc file?

Actions

UndeadBob Apr 12, 2010 12:27 PM

"
calcUF = library.UserFunctions("Calc")
calcUF.Call() '----------------------------- Errored Line
"

It looks like your only calling up one user function. What I meant was that if the initialization of variables was not in that user function.

I have a program that has an entire user object just to initialize all the variables I will need. If I tried to call an individual user function without those variables, it would definitely crash.

To attach, there should be an "Upload Attachment" tab just under the "Submit" button when you type your response. To include a link in your text, there should be an "inline" link.

Actions

tejas.dave Apr 12, 2010 9:35 PM

Hi,

I have attached error snap shot which i got in Microsoft Visual Studio 2008 and VEE Program. Please have a look at it.

Var_Calc.vee

Attachments

Var_Calc.vee19.9 KB
Untitled.jpg171.9 KB

Actions

MichaelWatts Apr 13, 2010 2:04 AM

I think the problem is that your Calc function has it's own display in it c.f. .NET control and therefore you need to provide an area in your VB program for it to appear. In the other way round i.e. .NET control in a VEE program you place the control onto a panel of some sorts and that is then 'painted' by the .NET code when the program runs.

In the first instance I would change your test to call a user function that purely deals with data e.g. send it a number and read the result. To do that of course you'll need to pass in the parameter(s) - in C# it is done with object arrays - and read the response.

Actions

tejas.dave Apr 13, 2010 11:10 PM

Sorry Boss, I didnt get your point. Can u please give me example of it?

Actions

UndeadBob Apr 14, 2010 12:49 PM

Basically, when you call your "Calc" VB is trying really hard to put that nice little panel somewhere. It's never going to find a good place for it until you give it one.

Instead of tackling that complicated problem, he suggests deleting the panel (right click on the title bar) and making the program functional without it.

I hope I understood that correctly to get you rolling until Michael gets back to explain it better.

Seriously, I would check his website for some awesome examples (listed in his profile). It helped me a LOT.

Actions

7 Replies

UndeadBob Apr 12, 2010 6:17 AM
Mark Correct
Correct Answer
Not having the VEE code, my first guess is regarding VEE's initialization of variables.

Could not resolve COM reference

Sounds like VEE is trying to call a variable that hasn't been initialized, or is otherwise used improperly.
Like • Show 0 Likes0
Actions
tejas.dave Apr 12, 2010 8:30 AM
Mark Correct
Correct Answer
Hi,

Thanks for your reply.

VEE code (with .Net in it) worked fine in VEE Pro 8.5. But When I called it from Visual basic it didnt work. I have given reference of Callable AciveX
Automation server and .Net assembly (in my case, System.Windows.Forms) in MS Visual Studio 2008 project. So I think there is no problem with initilization
of variables. Please tell me how do i attach VEE code or doc file?
Like • Show 0 Likes0
Actions
UndeadBob Apr 12, 2010 12:27 PM
Mark Correct
Correct Answer
"
calcUF = library.UserFunctions("Calc")
calcUF.Call() '----------------------------- Errored Line
"

It looks like your only calling up one user function. What I meant was that if the initialization of variables was not in that user function.

I have a program that has an entire user object just to initialize all the variables I will need. If I tried to call an individual user function without those variables, it would definitely crash.

To attach, there should be an "Upload Attachment" tab just under the "Submit" button when you type your response. To include a link in your text, there should be an "inline" link.
Like • Show 0 Likes0
Actions
tejas.dave Apr 12, 2010 9:35 PM
Mark Correct
Correct Answer
Hi,

I have attached error snap shot which i got in Microsoft Visual Studio 2008 and VEE Program. Please have a look at it. Var_Calc.vee
Attachments
- Var_Calc.vee19.9 KB
- Untitled.jpg171.9 KB
Like • Show 0 Likes0
Actions
MichaelWatts Apr 13, 2010 2:04 AM
Mark Correct
Correct Answer
I think the problem is that your Calc function has it's own display in it c.f. .NET control and therefore you need to provide an area in your VB program for it to appear. In the other way round i.e. .NET control in a VEE program you place the control onto a panel of some sorts and that is then 'painted' by the .NET code when the program runs.

In the first instance I would change your test to call a user function that purely deals with data e.g. send it a number and read the result. To do that of course you'll need to pass in the parameter(s) - in C# it is done with object arrays - and read the response.
Like • Show 0 Likes0
Actions
tejas.dave Apr 13, 2010 11:10 PM
Mark Correct
Correct Answer
Sorry Boss, I didnt get your point. Can u please give me example of it?
Like • Show 0 Likes0
Actions
UndeadBob Apr 14, 2010 12:49 PM
Mark Correct
Correct Answer
Basically, when you call your "Calc" VB is trying really hard to put that nice little panel somewhere. It's never going to find a good place for it until you give it one.

Instead of tackling that complicated problem, he suggests deleting the panel (right click on the title bar) and making the program functional without it.

I hope I understood that correctly to get you rolling until Michael gets back to explain it better.

Seriously, I would check his website for some awesome examples (listed in his profile). It helped me a LOT.
Like • Show 0 Likes0
Actions

Problem with integration of VEE objects into VB

Outcomes

Attachments

Related Content

Recommended Content