Re: RUNSQLSTM Source File Record Length -- 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: RUNSQLSTM Source File Record Length
From: Tom Liotta <qsrvbas@xxxxxxxxxxxx>
Date: Mon, 25 Jun 2007 11:46:24 -0700
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>

Jeff Young wrote:

If you want to have multiple statements in the source file, end your statement
with a semicolon (;).

Minor note... I generally insert a line containing only a semi-colon character after statements rather than adding the character to the end of a statement. It makes a decent visual delimiter as well as a valid statement delimiter. It can also ease programming if the statements are auto-generated. (Not much, but a little.)

Tom Liotta

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: RUNSQLSTM Source File Record Length , rob

This mailing list archive is Copyright 1997-2025 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.