From: chrislbaugh@hotmail.com (Chris Baugh) Newsgroups: comp.databases.oracle Subject: Re: Using Exception in a stored procedure when validating a date Date: 4 Apr 2002 11:12:14 -0800 Organization: http://groups.google.com/ Lines: 8 Message-ID: References: <52086d5b.0204031341.436d480a@posting.google.com> NNTP-Posting-Host: 213.122.123.41 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1017947534 7256 127.0.0.1 (4 Apr 2002 19:12:14 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 4 Apr 2002 19:12:14 GMT Have you tried surrounding the area of code using the to_date function in its own block. You can then trap any exception caused by the to_date, using an insert/delete statement when it fails. Using this method would ensure you colud continue the cursor loop, fetching the next row, to do the to_date on. Rather than entering the procedures exception handling, and being kicked out of the loop. This may help, unless I've misunderstood the query fully