Re: sql and screen fields -- RPG400-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: sql and screen fields
From: Sam_L <lennon_s_j@xxxxxxxxxxx>
Date: Fri, 11 Oct 2024 14:02:55 -0400
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

Save the pre-compiler output file and see how your screen field looks there. (Maybe it's a ref field or something odd.)

On 10/11/2024 1:30 PM, Jay Vaughn wrote:

Sam - came to mind and I tried rpgppopt(*lvl2) - but did not help.

Jay

On Fri, Oct 11, 2024 at 1:28 PM Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

Isn't there is a compile option that does additional pre-compiler
expansion of the source. Something like LEVEL1 or LEVEL2. Prompt the
command, don't have access now to try it.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: sql and screen fields , Jay Vaughn

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.