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") failed - The specified module could not be found"
A simple 'Dir *.dll' confirms that 'scinder.dll' is in the directory.
The content of the install.bat is as follows:
REM Installation for the scinder.dll and scoutdy.dll files
REM Windows 98/ME/XP/2003 server
echo About to install scinder.dll and scoutdy.dll. You will receive individual message confirmation of each install.
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?
Written by John Humphreys
C++ Threading and the POSIX Library
This article will cover the basic information that you need to know in order to make use of the POSIX threading library available for C and C++ on UNIX and most Linux systems.
Included as part of the C++ Standard Template Library (STL) is a collection of generic containers. Each of these containers serves a different purpose and has different pros and cons. It is often difficult to decide which container to use and …