Re: Debugging an SQL UDF -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Debugging an SQL UDF
From: Vern Hamberg <vhamberg@xxxxxxxxxxx>
Date: Wed, 20 Apr 2011 16:32:36 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

James

I don't know a tutorial - I've just used the Redbook on stored procedures, functions, and triggers. It has been enough.

HTH
Vern

On 4/20/2011 1:47 PM, James Lampert wrote:

Found the bug. And it turned out to be unspeakably stupid. There's a
statement at the beginning of the UDF, where I'm looking up an
enrollment number for the current user, and it turns out I was looking
it up for the wrong environment. Hardcoded as the wrong environment.

Time to consider a new career cleaning out stables.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.