Dll vs Visual Basic

[JDS2]

Hello,
I've got a smaal prob. I've written a dll in visual c++ using the rugular dll with shared mfc dll in the wizard options. This dll contains routines wich I use in Vb. The problem is that on my pc, everything is working fine, but when I make an installationfile and instaal it on an other pc, the application can't seem to find the dll, even when he's placed on the right path etc etc

Could someone help me out with this one??
ps: the app is running on a nt4 workstation

 

[Zyrenthian]

I assume that because it was working on your machine, you have the "import" for the dll in your app. Why it will not work seems a bit odd. Did you hard code the path into the import? (been a while since I have done VB so i dont even know if you CAN hard code a path) The next guess would be to put the dll in the directory of the app. After that, I would make sure that all the other dlls are on the computer. I remember problems I had porting my app and the machines I demo'd it on would need the VB Runtime Libraries. These are just a few places to look but I hope it helped

Matt

 

[JDS2]

I've solved the prob, now I use an static linked dll instead of an dynamicly linked and it seems to work. The only disadventidge is that the dll is now 1052kb big instead of 109kb ... but hey, it works

tanks anyway