Specify a VB DLL location instead of registring?

[JC Denton]

i ave created a dll and a tester program but the program cannot find the entry point stringEd

dll: [class module]

Option Explicit
Public Function stringEd()
    stringEd = "hello cheecky"
End Function

tester program:

declaration statement in module:

Declare Function stringEd Lib "C:\fabian\VB Projects\Mine\dll try\stringEd.dll" () As String

Private Sub Command1_Click()
MsgBox stringEd()
End Sub

thanx all!

[brucevde]

VB Dlls are COM Components. The Declare Function ... statement is for accessing "standard" dlls, usually written in C/C++, like the windows api.

With COM components you need to include a refererence to the dll in your project, create an "instance" of your class and then call the class properties/methods.

References - Project -> References menu

Private Sub Command1_Click()
    Dim oMyClassInstance as MyClassProject.MyClassName
    Set oMyClassInstance = MyClassProject.MyClassName
 
    msgbox oMyClassInstance.StringEd
 
    Set oMyClassInstance = Nothing 'releases memory 
End Sub

[JC Denton]

Thanx Brucevde

How can i make it so that the app will always be accustomed that the dll is in the same dir.... or e.g.

app.path & "\resources\stringEd.dll"

[frigginjerk]

Originally posted by JC Denton
Thanx Brucevde

How can i make it so that the app will always be accustomed that the dll is in the same dir.... or e.g.

app.path & "\resources\stringEd.dll"

you would have to use late-binding.

What brucevde is talking about is called early-binding. It's called early-binding because you app will have a reference to the dll before your app is compiled.

late-binding allows you to create com objects in you app without it having a reference before your app is compiled. However, you still need to know the library and class names. But I don't think you can specifiy the filepath of the dll, I'm pretty sure that the vb runtime will search the registry for its filepath.