VC>>> By my understanding, it should have done unless one of you is VC>>> using different products to build it and therefore one of them is VC>>> producing incorrect CRCs or definately the CRC tables within the VC>>> program/s are not the same.
There was no parrallel production distributed. Ward used the last Nodelist I distributed when he took over and produced the next nodediff and nodelist. The combination of my last nodelist and Ward's nodediff produced a perfect next nodelist.
>> Isn't it so that the slightest difference, for example an extra space >> or so, could generate the problem while for the eye the data is the >> same?
VC> Yep, that would do it :)
VC> However seeing as it is an automated system by which all segments are VC> uploaded to the specific system that then processes them producing a new VC> list then there should NOT be any instance of extra spaces or for that VC> matter any thing else.
VC> Or am I being to automated ?
The source files are not always identical. Difference can occur when e.g. region or zone updates are to late to be included on one system and in time for the other.
Changes to CPY, Pro and epilog, as well as changes to the Zone header section are always a day behind on my system.
But all this is irrelevant to change overs that have recently been made.
If the checksum of the previous nodelist does not match the checksum in de nodediff, then you are either using a wrong nodelist or a wrong nodediff.
Kees
--- GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
