deploying labview dll for vb6

[GertW]

Hello,

I have created a labview DLL that uses the modulation toolkit. The idea is to use this dll in a VB6 project and this on a PC that doesn't have anything installed from Labview, only visual basic 6.

To test my DLL, i have created a VB6 test project on my development PC (with labview + modulation toolkit installed) which calls this DLL. On my development PC everything is working fine. The problem starts when I try to run this VB6 project on a PC without Labview. First, he asked for the labview runtime engine, so I installed this and restarted my VB6 project. But if I try to run my project VB6 automatically shuts down.

How can I create a VB6 project on a blank PC that uses my labview DLL?

Thanks

[smercurio_fc]

I would start out with a simple project just to make sure you understand how to get LabVIEW DLLs working in VB6, and then work your way up to getting the full thing working. There could be any number of reasons why VB6 is crashing, given it's so old. I would start here: Calling LabVIEW created dll from Visual Basic 6.

Also, you should be aware that the Modulation Toolkit requires a deployment license.

[GertW]

My DLL is working fine on my development PC. I have created a VB6 project that uses this DLL and it is running without any problems. The problem starts when I want to run my VB6 project on a PC without labview (a blank PC with only VB6 on it).

[smercurio_fc]

Well, as you've already found out, you have to have the LabVIEW Run Time Engine installed on this other PC. This is an absolute requirement.

Unfortunately, right now there's too many variables, so the only other answer I can give you is that you should try to narrow this problem down by creating a simplified LabVIEW DLL and try to call it in your VB6 on this other computer. To be honest, I'm not sure whether not having the deployment license for the Modulation Toolkit on this other machine would actually cause VB6 to crash. I did a search on this site and didn't find anything. Still, I would suggest trying it out with the Modulation Toolkit first,  Then work your way up until you find where it breaks.