Hi,
You could try to put the suspect vi in the true state of a case, and wire
false to it (in the original sequence). You could put a few minutes wait in
the true case. If it still crashes, it's not the vi, but a late reaction of
the dll. Just to make sure...
The VI does't crash when you run it alone. Does it crash when it's called
from the sequence, but without the inputs wired? Perhaps the crash relates
to an input value.
If it is the VI, we still need more info; e.g. are there large arrays, shift
registers (esp. unwire from outside), etc.
Regards,
Wiebe.
"marino"
wrote in message
news:506500000005000000AECA0000-1042324653000@exchange.ni.com...
> yes...
>
> Before I call the vi, I use a dll (written in delphi) to access
>
databases. But I don't think the dll causes this because we've been
> using it for years.
> The vi is a part of a sequence of vi's. First I call a couple of vi's
> which use the dll, and then I call the vi (which closes labview
> automatically after a few minutes or seconds) This vi doens't use any
> dll's.
>
> best regards,
> Marino