Hi,
Not this time. We do not have any protection against closing WA
from any user code (i.e. key/for/filter/relation expressions or
from error handler) when it's used by RDD code :-(
Yes, I understand the problem. I've used to call DBCLOSEAREA() in my
error block. This exploits the problem o
On Tue, 18 May 2010, Mindaugas Kavaliauskas wrote:
Hi,
> >This is expected and documented few times on this list behavior.
> >Of course it's a bug but it cannot be well fixed without very serious
> >modifications in RDD code and all code (also 3-rd part one) which
> >access any RDD methods.
> >It
Hi,
On 2010.05.18 15:00, Przemysław Czerpak wrote:
3 similar samples with different error, so, perhaps we have memory
corruption here.
This is expected and documented few times on this list behavior.
Of course it's a bug but it cannot be well fixed without very serious
modifications in RDD co
On Tue, 18 May 2010, Mindaugas Kavaliauskas wrote:
Hi,
> 3 similar samples with different error, so, perhaps we have memory
> corruption here.
This is expected and documented few times on this list behavior.
Of course it's a bug but it cannot be well fixed without very serious
modifications in R
Hi,
3 similar samples with different error, so, perhaps we have memory
corruption here.
Regards,
Mindaugas
C:\cawi32\sample\test>cat test203.prg
STATIC indexBlocks := {}
PROC MAIN()
DBCREATE("test203.dbf", {{"F", "C", 1, 0}}, "DBFCDX", .T.)
FERASE("tmp.cdx")
AADD(indexBlocks, {|| FIE
