Re: Calling VB DLL from Delphi - Access Violation Error In Delphi After DLL is rebuilt?
- From: erewhon@xxxxxxxxxx (J French)
- Date: Sat, 23 Apr 2005 10:20:47 +0000 (UTC)
On Fri, 22 Apr 2005 14:14:58 +0100, "Andrew Oborn" <v834@xxxxxxxxxxx>
wrote:
<snip>
>
>However.......
>
>As/when the VB DLL is recompiled (which, when I come to using this for
>something more practical, may be the case), when I next come to run the
>delphi form, I get an exception EIntfCastError with message 'Interface not
>supported'. The only solution to get this working again is to re-import the
>type library into the project - but, once deployed, the DLL (in this case
>from another application) may be updated and I don't really want to have to
>make sure my delphi program is updated every time (working on the assumption
>that just because the DLL is updated, existing functionality is not changed,
>only new stuff added).
>
>Any thoughts on how I get round this? Presumably it's something to do with
>the DLL version?
Try setting the VB DLL's project to Binary Compatibility
.
- Follow-Ups:
- References:
- Prev by Date: Re: How to add control to form?
- Next by Date: Re: Auto Fill Web Forms
- Previous by thread: Calling VB DLL from Delphi - Access Violation Error In Delphi After DLL is rebuilt?
- Next by thread: Re: Calling VB DLL from Delphi - Access Violation Error In Delphi After DLL is rebuilt?
- Index(es):
Relevant Pages
|
