File restructure bastardization

[Kenneth Brody]

Quoting George Simon (Fri, 23 Sep 2005 13:20:49 -0400):

> > -----Original Message-----
> > From: Kenneth Brody [mailto:kenbrody at bestweb.net]
> > Sent: Thursday, September 22, 2005 12:46 PM
> > To: George Simon
> > Cc: 'filePro List'
> > Subject: RE: File restructure bastardization
> >
> > Quoting George Simon (Thu, 22 Sep 2005 11:36:58 -0400):
> > [...]
> > > > ObDisclaimer:  This is not an official endorsement by fPTech, just
> > > > my own opinion.
> > > >
> > > > Since you aren't changing the length of the fields, and the new
> type
> > > > would accept the existing data as-is, with no effect on sort-order
> > > > (in case there are indexes built on them), you could theoretically
> > > > edit the map, changing "YESNO" to "*" or "ALLUP", even while
> people
> > > > are using the file, with no ill effect.
> > > >
> > > > Of course, I would highly recommend trying this out on a test file
> > > > first.
> > [...]
> > > Any time I've changed a field edit from anything to an asterisk,
> > > re-structuring does not take place.  I don't think (know?) that is
> true
> > > for ALLUP.
> >
> > Changing a field type to "*" without changing its length does not
> > trigger a restructure, as the field's contents would not change
> > during such a restructure.
>
> That's what I said but, to me, it seemed that you implied that this is
> also true for the ALLUP edit.

Changing from YESNO to ALLUP in ddefine will trigger a restructure.
However, since the current edit is a single upper-case letter, the
net result will be that no change will be made to the data by that
restructure.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com