Without a lot more detail it's hard to know what's
happening here.
But from your description I'd guess that a unit is explicitly
destroying something in it's finalisation section that is
automatically destroyed (or about to be destroyed) by the
framework. Remember that "owned" components don't need to
be explicitly destroyed.
So one of you is stepping on the other's toes.
-ns
----- Original Message -----
From: "Moises Lopez" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent: Friday, June 15, 2001 6:34 AM
Subject: [DUG]: Closing app on Win2K
> hi there,
> i have an app that when its finished, after destroying
> all its datamodules and the main form, and the
> finalization section of an unit, i get an
> EAccessViolation when running the app on Win2K.
>
> well i also got it in my NT computer so its not
> strictly 2k
>
> so im kind of wondering if that is standard operating
> procedure on part of M$..
>
> any hints welcome.
> in the meantime (spacehog) i'll be looking around..
>
> TIA
>
> Moises Lopez
>
> __________________________________________________
> Do You Yahoo!?
> Spot the hottest trends in music, movies, and more.
> http://buzz.yahoo.com/
> --------------------------------------------------------------------------
-
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
> To UnSub, send email to: [EMAIL PROTECTED]
> with body of "unsubscribe delphi"
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
