file not found, but its there!!!

I have built an application that is self-contained. The only thing is a dll call function to open a file with a win98 style window. on my computer everything is fine. but on the computer the application is meant to be run, i get a problem, because the comdlg32.dll is too old. Wanting to get rid of the problem, i took a good version of the dll and renamed it dllfile.dll . On my computer everything is great. i can even change the name of the dllfile then get an error 48 missing dll file (its true it is missing if i rename it volontarly) but on the other computer, the file is never found, and i get an error 53 file not found... how could it be a different error, i tried to add a specific path for the library file in the module, but the same thing happens... it tell me : cannot find c:\progpath\dllfile.dll
but c:\progpath\dllfile.dll does exist, could there be something missing like a dependency. i tried putting the dll file in c:\; c:\winnt\system; c:\winnt\system32; c:\propath\
to cover all of the possible path the app could mistakenly go.

hope you can give me input because im out of idea...

the working computer is a win98 machine
the non working computer is a winnt 4 workstation sp3
could sp6 help???
njacquesAsked:
Who is Participating?
 
GunsenConnect With a Mentor Commented:
U could try copying all   comdlg32.*   files (.dep, .dll, .ocx)  to system32,  then   regsvr32 c:\win98\system32\comdlg32.ocx
0
 
mark2150Commented:
Copying .DLL's doesn't WORK. You have to REGISTER them.

The correct way to handle this is to build an install kit and run SETUP. This will bring all the .DLLs into sych *and* register them.

M
0
 
njacquesAuthor Commented:
The problem is that the target computer is a machine at the office, that the computer guys dont want me to put all sort of versions of dll, not wanting to have to re-install all the machine all over again... I have faith that updating dll files will work, but i have to wait that they update the WinNT Workstation 4 sp3 to sp5 or 6 (they dont know which) before Y2K. to see how it will work... i could come will my install pack, but i want minimal operations, right now, i just copy my exe to the path i want, no install... but the registering is a good idea... ill try that....
coming forward with more input soon....
0
 
mark2150Commented:
You've gotta do the install the first time. When you do the install it'll create a little text file in the directory where the app is that contains the summary of what was registered and what wasn't. This is used by uninstaller to unwind what your app did. Copy *THAT* file and give it to the IT guys and they'll have a nice, neat record of what was done. It tells what .DLL's were updated, what ones were already up to date, etc. ST5UNST.LOG is what VB5 calls it, I'm not sure what VB6 names it as, but most times it's the only other file in the program directory beside your .EXE and anything else you included in the app.

Give the IT folx a copy of the setup kit for *their* records so they can reinstall if necessary.

M
0
All Courses

From novice to tech pro — start learning today.