Marc,
there can be several issues which can create unexpected behaviour of
the application. especially the point that the lib-file creates
compilation-errors is very....strange. this should not happen if the
DLL has been created in a proper way.
i asume that these errors are either linker-errors or "unknown
function"-errors. in general, the lib-file contains the info for the
developement system where the individual functions can be found within
the DLL. so either there is a problem that the calling convention does
not fit at all or (regarding the lib-file) it does not match the DLL at
all (version-infos?).
the calling convention-problem can create runtime-errors as well, since
it specifies the way how parameters are passed to and from the stack.
so in general, there can occur a general protection fault when passing
an array or string in the wrong calling convention. the big question
is, why does it work in debug?
afaik there is no special difference between debug and release except
the debugging-capabilities, which create an overhead to the code and,
maybe the reason here, a slightly different timing-behaviour. maybe you
should add waiting-functions here and there just to check that
possibility. and, of course, you should check the compiler-options.
Norbert B.
- NI Germany
Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
