Hello,
Here is my problem. I am running a VB 4.0 16-bit client on a WIndows 95/98/NT environment along with a VC++ 1.52 dll. This component retrieves the user's login in Novell, which is used on top of the Windows platform. I have been told to test the app on a Windows 2000 machine and this without the Novell. THe implementation is obviously different and it handles the mpr.dll instead for the login info. However, the client does not seem to "see" the DLL. I am following the same steps I did for the other platforms which work perfectly. If I comment out the DLL function call in the client, it works fine. The error that is returned is that it can't find the dll.
This is what I already tried:
1) Debugged the DLL and saw that it does not even go in it.
2) Tried to register it with regsrv32
3) Tried putting the dll in the System and System32 directories.
4) Put the whole path in the declaration.
Am I wasting my time thinking that a 16-bit DLL will work on Win2K? Please help
Spinik
Spinik
Senior consultant
Here is my problem. I am running a VB 4.0 16-bit client on a WIndows 95/98/NT environment along with a VC++ 1.52 dll. This component retrieves the user's login in Novell, which is used on top of the Windows platform. I have been told to test the app on a Windows 2000 machine and this without the Novell. THe implementation is obviously different and it handles the mpr.dll instead for the login info. However, the client does not seem to "see" the DLL. I am following the same steps I did for the other platforms which work perfectly. If I comment out the DLL function call in the client, it works fine. The error that is returned is that it can't find the dll.
This is what I already tried:
1) Debugged the DLL and saw that it does not even go in it.
2) Tried to register it with regsrv32
3) Tried putting the dll in the System and System32 directories.
4) Put the whole path in the declaration.
Am I wasting my time thinking that a 16-bit DLL will work on Win2K? Please help
Spinik
Spinik
Senior consultant