From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,efa909d1c194c363
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-10-20 04:41:12 PST
Newsgroups: comp.lang.ada
Path: 
 bga.com!news.sprintlink.net!howland.reston.ans.net!EU.net!chsun!mlma11.matrix.ch!user
From: Mats.Weber@matrix.ch (Mats Weber)
Subject: Re: delay duration'last: problems?
Message-ID: <Mats.Weber-2010941153120001@mlma11.matrix.ch>
Sender: usenet@eunet.ch
Organization: ELCA Matrix SA
References: <H.eg.yfQlZ_ydPoc@mbase97.xs4all.nl>
Date: Thu, 20 Oct 1994 10:53:12 GMT
Date: 1994-10-20T10:53:12+00:00
List-Id: <comp.lang.ada>

We also had problems with this, but not on VMS. We simply changed the
delays to less than 86_400.0 seconds and everything went fine.

Another thing that you must beware of on VMS is the Timer Queue Entry
Quota (tqelm in autohorize) which must be greater than the maximum number
of pending delays in your program.

I don't know what can cause the access violation.