|
-
Nov 28th, 2004, 04:01 PM
#1
Thread Starter
Frenzied Member
Component (DLL) Question
Hello, I was asked for a class to develop a component.
What this component has to have is an interfase and its contract.
So I began with an ActiveX DLL project... How would I develop the interface? Or am I doing the wrong thing? In our classes we were told Components didn't behave like Objects but I have this:
VB Code:
Option Explicit
Private Sub Form_Load()
Dim myComponent As VBToExcel
Set myComponent = New VBToExcel
myComponent.DoSomething
Set myComponent = Nothing
End Sub
What am I missing? Did I mess it up? I mean, the code is working but it shouldn't be done like that, should it?
Last edited by Tec-Nico; Nov 28th, 2004 at 04:07 PM.
We miss you, friend...  Rest in Peace, we will take care of the rest of it.
[vbcode]
On Error Me.Fault = False
[/vbcode]
- Silence is the human way to share ignorance
Tec-Nico
-
Nov 28th, 2004, 11:31 PM
#2
Thread Starter
Frenzied Member
I have made some research and found this page. I have implemented the Interface as the article says I should...
Article
But I still have this doubt? Is this the right thing to do? Could anyone please answer that question?
What I am saying is that in C++ you make your ISomething.h as your Interface, but is this even done in VB? (Not that I am complaining that the code isn't working or anything, but you know how proffesors can be)
Thanks in advance.
We miss you, friend...  Rest in Peace, we will take care of the rest of it.
[vbcode]
On Error Me.Fault = False
[/vbcode]
- Silence is the human way to share ignorance
Tec-Nico
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
|