Antonio,
In the begin of this post I have included the content of HB_OUT.log.
IF I comment HB_GCALL( ) on method End() of dialog.prg everything works fine.
ACTIVEX ACCESS_VIOLATION
-
Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Re: ACTIVEX ACCESS_VIOLATION
have you considered to create an external EXE using your PRG code and call it for each document ?
That way the memory of your app and the memory used by such OCX will not conflict.
I see it is a private OCX, have you contacted its developers for help ?
That way the memory of your app and the memory used by such OCX will not conflict.
I see it is a private OCX, have you contacted its developers for help ?
Re: ACTIVEX ACCESS_VIOLATION
Antonio,
have you considered to create an external EXE using your PRG code and call it for each document ? That way the memory of your app and the memory used by such OCX will not conflict.
No, because I have to interact with the ocx created, add files, doing merge, etc
I see it is a private OCX, have you contacted its developers for help ?
Yes it was the first thing I did, but they told that don't have this kind of problem with any other language !
Important - I use this OCX since when I was working with FW/Clipper(different version of course). WIth Harbour I come using it since 2014 without problems. The problem has start from FWH1707.
have you considered to create an external EXE using your PRG code and call it for each document ? That way the memory of your app and the memory used by such OCX will not conflict.
No, because I have to interact with the ocx created, add files, doing merge, etc
I see it is a private OCX, have you contacted its developers for help ?
Yes it was the first thing I did, but they told that don't have this kind of problem with any other language !
Important - I use this OCX since when I was working with FW/Clipper(different version of course). WIth Harbour I come using it since 2014 without problems. The problem has start from FWH1707.