× 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: PRTF problem...fields don't go where I want 'em
  • From: gloffk <gloffk@xxxxxxxxxx>
  • Date: Mon, 08 Feb 1999 17:49:30 -0500

I definitely only have one printer file with that name.

I have the correct printer file name in my F-specs.

I am specifying the starting position not the ending position for the field.

I recompiled the DDS.

Any other ideas?

Thanks for the reply.

"Stone, Brad V (TC)" wrote:

> Just a thought..
>
> Make sure you only have one printer file with that name in your library
> list.
>
> Make sure you specified the correct printer file name in your F-Specs.
>
> Make sure you are specifying the starting posistion, not the ending
> postition (o-specs use ending position) in your DDS.
>
> Make sure to recompile the DDS.
>
> Bradley V. Stone
> Taylor Corporation - OASIS Programmer/Analyst
> bvstone@taylorcorp.com
>
> > -----Original Message-----
> > From: Kevin [SMTP:gloffk@grcarc.org]
> > Sent: Monday, February 08, 1999 1:12 PM
> > To:   Midrange List server
> > Subject:      PRTF problem...fields don't go where I want 'em
> >
> > I am trying to modify a prtf to add a couple of fields to it. I can add
> > the fields just fine using either RLU or SEU. In RLU they look right
> > where I want them. When I generate the file using RLU they again are in
> > the exact place where I want them. However, when I run the report using
> > my new version of the prtf the fields are on the wrong line and in the
> > wrong column. The text that I have put in however is in the right place.
> > For example, if I want to place birthdate in the report. The heading
> > 'birthdate' will be right where I put it and want it. But the field
> > Birthdate will be one line down and several spaces to the right. Can
> > someone tell me what I am missing here? Any and all help would be
> > greatly appreciated.
> >
> > Kevin Gloff
> >
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> > MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
> > david@midrange.com
> > +---
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.