File restructure bastardization

[Nancy Palmquist]

Kenneth Brody wrote:
> 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.

But the lockfile will not allow this kind of change if the file is in 
use as indicated by the original posting.  The only way to change the 
map would be from outside of filePro.

I agree with all others - this is a very touchy type of change.  If you 
make any other change to the map your customers may crash entirely and 
the data become corrupt.

I would suggest this be handled during the scheduled maintenance time.

Nancy

-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com