× 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: changing field descriptions
  • From: "Nelson C. Smith" <ncsmith@xxxxxxxx>
  • Date: Fri, 4 Feb 2000 15:46:55 -0500

It's a "Feature", not a bug.

----- Original Message -----
From: "Reger, Bill" <breger@levitz.com>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, February 04, 2000 11:52 AM
Subject: RE: changing field descriptions


> WRKDBF used to have this problem too until I started looking at the file's
> create/change date and time.  You should report this problem to EZVIEW and
> Questview's authors, like others did to me with WRKDBF.  It's not
difficult
> to fix.
>
> William K. Reger
> Senior Project Manager
> Levitz Furniture Corporation
> Phone:  (561) 994-5114
> E-mail:  breger@levitz.com <mailto:breger@levitz.com>
>
> -----Original Message-----
> From: Scott Mildenberger [mailto:Smildenber@Washcorp.com]
> Sent: Friday, February 04, 2000 10:07 AM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: changing field descriptions
>
> Jo Ann,
> It is very likely that EZVIEW saves it's values and
> doesn't re-read
> them from the file description if you are accessing the same
> file that you
> previously were using.  We use Questview and it acts this
> same way.  If you
> switch to a different file and then come back you may see
> the new
> descriptions.  Or the next day, you will see the new ones.
> I know in
> Questview I can force it by having it look for a file that
> doesn't exist and
> then go back to the one I'm interested in.  By the way, this
> also happens
> when changing field sizes/definitions or adding new fields
> which can result
> in some funny looking data that doesn't actually reflect
> what is in your
> file.
>
> Scott Mildenberger
>
> > -----Original Message-----
> > From: burelle@bigy.com [SMTP:burelle@bigy.com]
> > Sent: Friday, February 04, 2000 6:13 AM
> > To: midrange-l@midrange.com
> > Subject: FW: changing field descriptions
> >
> > Dan;
> >
> > I changed my dds source from COLHDG('FILLER 5') to
> COLHDG('EXPIRATION
> > DATE' 'NEEDED'), prompted the CHGPF command, made sure my
> sourcefile and
> > library where in SRCFILE, made DLTDEPLF *NO.  It took
> awhile, said it
> > changed, but when I looked at if with EZVIEW I saw the
> same description,
> > but when I did a QUERY over that file I saw the new
> description.
> >
> > So, THANK YOU 8-))).  I also did a dspffd and saw the new
> description, any
> > idea where EZVIEW gets it field descriptions?
> >
> > Jo Ann
> >  ----------
> > From: DBale@TFSA.Textron.com
> > To: MIDRANGE-L@midrange.com
> > Cc: Burelle, Jo Ann Ext-785
> > Subject: RE: changing field descriptions
> > Date: Thursday, February 03, 2000 4:57PM
> > Priority: High
> >
> > The newest (V3R7 and higher???) incarnations of CHGPF
> (that's _Change_
> > Physical File) allow you to "recompile" the file object
> and keep the data
> > and handle the logical files.  It's no longer a pipe
> dream!
> >
> > Look for the Source file (SRCFILE) and Delete dependent
> logical file
> > (DLTDEPLF) parameters on the command and prompt for the
> help text on them.
> >
> >  - Dan Bale
> >
> >  -----Original Message-----
> > From: burelle@bigy.com [mailto:burelle@bigy.com]
> > Sent: Thursday, February 03, 2000 3:50 PM
> > To: midrange-l@midrange.com
> > Subject: changing field descriptions
> >
> >
> > Hi;
> >
> > Somewhere in the cobwebs of my mind I remember reading how
> you can change
> > the field description of a file without needing to do
> messing things like,
> > delete all the logicals, save the file, re-compile the
> file, re-compile
> > the
> > logicals (remembering level check *NO), etc...  Is this
> just wishful
> > thinking?
> >
> > Jo Ann
> > +---
> > | 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
> +---
> +---
> | 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 ...

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.