gawilson2000
asked on
Trouble registering some DLLs we created
My company has produced a couple of DLLs written in Visual C++ - for use within some MS Access databases.
These DLLs are turning out to be quite temperamental when it comes to installing them on target PCs.
I am using Windows XP and one of our customers is using Windows Server 2000 - and we are both having the following trouble:
1. Place the DLLs and installation batch file in the same directory.
2. Navigate to this directory using the DOS prompt.
3. Execute batch file.
The following error occurs:
"LoadLibrary("scinder.dll"
A simple 'Dir *.dll' confirms that 'scinder.dll' is in the directory.
The content of the install.bat is as follows:
@echo off
REM Installation for the scinder.dll and scoutdy.dll files
REM Windows 98/ME/XP/2003 server
path=%path%;%windir%\syste
echo About to install scinder.dll and scoutdy.dll. You will receive individual message confirmation of each install.
pause
regsvr32 scinder.dll
regsvr32 scoutdy.dll
echo Installation complete.
Have we missed something when compiling these DLLs? I have heard also of 'self-registering' DLLs - is there a way that we can simply place the DLLs in a customer's System32 directory and have them working without having to execute regsvr32?
These DLLs are turning out to be quite temperamental when it comes to installing them on target PCs.
I am using Windows XP and one of our customers is using Windows Server 2000 - and we are both having the following trouble:
1. Place the DLLs and installation batch file in the same directory.
2. Navigate to this directory using the DOS prompt.
3. Execute batch file.
The following error occurs:
"LoadLibrary("scinder.dll"
A simple 'Dir *.dll' confirms that 'scinder.dll' is in the directory.
The content of the install.bat is as follows:
@echo off
REM Installation for the scinder.dll and scoutdy.dll files
REM Windows 98/ME/XP/2003 server
path=%path%;%windir%\syste
echo About to install scinder.dll and scoutdy.dll. You will receive individual message confirmation of each install.
pause
regsvr32 scinder.dll
regsvr32 scoutdy.dll
echo Installation complete.
Have we missed something when compiling these DLLs? I have heard also of 'self-registering' DLLs - is there a way that we can simply place the DLLs in a customer's System32 directory and have them working without having to execute regsvr32?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That was actually what I was referring to - a missing DLL on the target system. Why did you need nomeone else's suggestion? :o)
ASKER
I wouldn't have - but I received their suggestion before yours.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The strange thing was that I was able to place this DLL into System32 and it worked immediately. So, getting back to the second part of me question, why is it that this one doesn't need regsvr32 - but the DLLs we created do?