exposing parameters for OBject

O.K. I'm getting a little desperate now.

I have a dll that comes with a VB interface and does exactly what I want but on a one-time basis. What I am trying to do is get the vb interface to run from the command line or through code and that's just not happening yet.

This dll converts images and since I'm not a VB guru I need to (i think) write a COM object to connect to the DLL and process a batch of files.

If I can get this to work, then I'll purchase the DLL. Until now, I haven't been able to do it. Any suggestions?

garry

I am sticking my neck out here...

...I like vague!

Does the dll have a I interface?

The way (this is the neck sticking bit) I have done this before, with dll 's written in house is to set a reference to the Interface and code against the object.

Code:

---

Private myObject as ISomeObject
...

Set myObject = New CSomeObject

---

This is most likely completely wrong and I'll get SLATED by 'The Guru's', but seeing as they have been out-to-lunch for the past two days, I'd thought I'd give it a go!

Enjoy!

Quote:

---

What I am trying to do is get the vb interface to run from the command line or through code and that's just not happening yet.

---

Can you expand on this?

VB can easily use DLLs that are not COM objects. People are using MFC DLLs which are written in C++ every day. COM is not needed.

Dave

Nor is MFC :)

O.K. guys I thinik I might explain a little more here.

I have a dll that I had a developer code for me. Now that the developer is not longer here, I don't have access to the uncompiled code for the dll. I DO have a vb app that accesses the code.

However, two problems with the vb app. It only allows me to convert a single image/file/other at a time instead of a directory listing of all images/files/others and; all the functions are private, without scripting support.

I have a developer writing a new interface for command line support but I had hoped to make this new vb app scriptable.

Does that explain it better?:sick:

Quote:

---

Originally posted by hexeliebe

... but I had hoped to make this new vb app scriptable.

---

Could you expand on this?

Basically what I was trying to say was that if you have yourself a DLL then you can "un-hitch" it from your current VB app and "hitch" it to any new or old VB app.

You can do whatever you want with it.

Dave

That's what I thought. So I guess I'll go out and find a new programmer

I guess my point was that the DLL that you have is still useable - as long as you have documentation on how to use it from the outside world (and it works), you dont need the source code.

Any decent VB programmer can "hook" into the DLL with above said doc's.

What do you need a new programmer for?

Dave

Because I'm not a 'decent vb programmer' and there is no documentation. Just sample VB code.

Also, I'm wanting to take this DLL to the 'next level' and incorporate it's functionality into a Powerpoint addin that will upload the active PPT to our service, convert it then send it to where it needs to go.

I'm a peculiar fellow I know, but the client is wanting this and since they pay the bills, I just smile and say "YES SIR!".

I was looking to get in contact with you directly about this, but you do not have a "PM" or personal messaging link attached to your name. If you are looking for help, feel free to contact me via PM or I can post my email as well.

Dave