Filepro Unix upgrade

[Kenneth Brody]

Quoting Christopher Yerry (Tue, 7 Feb 2006 07:09:06 -0800 (PST)):
[...Advice on moving from 4.8 on old system to 5.0 on new system...]

[...]
> 4 Destroy all filepro filelocks
>     { find /appl/filepro -name lockfile -rm {} \;  )

Not necessary if no one was in the file when you copied it over (and
no one should be in it), but "it couldn't hurt".

> 5 open
>         EVERY PIECE OF CODE AND RE SAVE IT (esc) (esc)
>         OPEN EVERY REPORT AND RE SAVE IT(esc) (esc)
>                the reports may give you an error on
>                opening save (esc) (esc) them it will
>                go away
>         Open every screen and save it.

I'm not sure why you would want to go through this hassle.  Unless you
did something to corrupt the file copying it over (in which case you're
going to want to copy it again, not simply resave the corrupted file),
there is no need to do this.

[...]
> 6) RE INDEX EVERY FILE (should I say that again)
[...]
> - I actually would recommend recording the structure
> every index destroying them and re creating them but
> I'm a fanatic

Destroy and recreate is a bit overkill, but rebuilding the indexes may
not be a bad idea.  If you happen to have a corrupted index because of
an old version of 4.8, rebuilding it with 5.0 will fix it.  (Of course,
the act of copying it doesn't introduce any problems that weren't there
already.)

[... Snip good idea of running old and new in parallel, which is ...]
[... usually a good idea for any system replacement.             ...]

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