RE: Changing an SQL table (Best practices)

Sounds like ALDON does it the same way we all used to before the days of 
CHGPF.  Copy or rename the original to something.  CRTPF the new file. 
Copy the data into it.
Judging by the resetting of the sequence number back to 1 I suspect that 
Turnover does the same thing.

Since they are already not doing ALTER TABLE, (which I sure wouldn't want 
to figure out how to do that by doing a comparison of an old and a new 
version of the CREATE TABLE source member), then I wonder if there is a 
way to include the sequence attribute on a mass INSERT versus a CPYF?

Rob Berendt