Search results for query: *

Thanks Chris, I tried putting the VB app in the system32 folder, but that doesn't work. This is what works, which I thought would never work: Before calling any DLL function, use the Chdir "path to the pcshll32.dll" statement. Everything works OK after that. VB can be strange...

Chris, you have come to the same conclusion I have: somehow PCOMM can find the DLL and subs, but the VB app can't. There is nothing in the path variable for this DLL(on either machine), and it and all subDLL'd, except the Win2Ks are located in the default PCOMM folder. I did as an experiment...

Thanks again Chris. PCOMM is running OK on this machine. No other VB apps using this DLL will run. However, the same VB apps will run on a different Win 2000 machine(also with PCOMM). Do you think PCOMM itself uses all of the same DLL's and that if it runs the DLL's used by VB are OK? Greg

Thanks Chris, very helpful. I have run depends.exe and found no errors in dependencies. However, your comment about versions of files may be the key. Do you mean all dll sublibraries must have the same version #? If so how do I find the version ? I noticed from depends that some of the...

Thanks, ngiz for link, but the solution suggested there is to have the dll in the default emulation folder. My dll is in the default emulation folder already. gswetzel@pplweb.com greg

DLL is pcshll32.dll, which is from IBM's PCOMM, a 3270, mainframe terminal emulation program for PC's. Greg

SemperFi is correct about not having to register non COM DLL's, which is my situation. My problem began when I tried to use the same VB program and DLL in Windows 2000(from 95). Something in the install of Win 2000 changed the configuration, which caused the failure of the VB program, but I...

Thanks, I've tried registering with regsvr32, but get message 'Load Library failed'. Another application uses this library successfully in Windows 2000.(but I don't know how or have source). Greg

In my VB6 project I am referencing a dll which produces a 'file not found' error on a Windows 2000 machine. The same program runs fine on Win 95 & 98. I tried putting the dll in different folders, using the fully qualified path in the declaration, but still get the error. The error occurs when...

I am curious about why you would want to compile an Excel VBA program? Added security? For either suggested approach in the reply, you would need the Excel object library. I have used the 'alternative' suggested with success, and secured the Excel VBA with passwords.

I too have found Excel97 links to be quirky, but with care can be useful. Excel seems to have special sensitivity to drive paths, escpecally if using Microsoft networking software(strangely Novell is more reliable). I never use a mapped drive letter in the link, but rather the full network...