I have just found a problem using SpeedButtons in a DLL.  My DLL is being
called by a foreign application not written using DELPHI.  The use of a
SpeedButton or a BitBtn to activate a function in the calling
application's DLL causes an error in the DELPHI DLL.  Using a plain
Button for the same call works without any problems at all.  Is there a
difference in the way these buttons work?  Is there a conflict when using
SpeedButtons with non DELPHI applications.  Has anybody experienced the
same problem?  If so is there a work around.  Borland's tech support
doesn't have a clue as to why this may be happening.

--
Alexander Medwedew
Computer Ventures, Inc.
compv...@tribeca.ios.com
http://tribeca.ios.com/~compvent/